Thx for clearing this up but i meant it makes no sense to cache a value NULL but the stream is online and was live 2hours before and 2hours after the occuring “offline” event without any change of “created_at” so the stream really was never offline but the api says it was for several minutes.
Caching makes always sense, yes, but it makes absolutely no sense if the data behind the cache is not perfectly valid.
Another example why caching is not a explanation for this issue:
If you call kraken/streams endpoint every 5s the viewer count always changes if there were changes of viewers on the stream, so i don’t think all the data is cached in that endpoint anyways so why cache it when its “NULL”.
Maybe cache is a problem here for extending the offline-but-online-period but its not the original source of this issue.