Simply-Stream

Beta

Caching Problem

8/26/2026 changelog

Hi everyone!

I'm currently in the process of migrating my system to a new server infrastructure and putting a few protective measures in place, since I've been seeing an extremely high volume of malicious bots lately (several thousand requests per day).

Unfortunately, I made a small mistake along the way! So if you opened the randomizer on August 26 before roughly 5 PM, you were probably shown one single clip of mine every time. This was partly down to the bot protection I added, which cached the response to requests far too aggressively. Globally, for everyone. From the very first request... And since I also have a status page at https://uptime.simply-stream.com/status/simply-stream that checks at regular intervals whether the site is still working as expected, a clip of mine was the first request to hit the randomizer — and that apparently got served to everyone who opened it afterwards.

If this happened to you: the problem is fixed now. If you open the link to your configured (or anonymous) randomizer in your browser's private mode, it should work as usual. In OBS it's a bit more stubborn, unfortunately. There it's enough to append something to the URL — for example &asdf. After that everything should be back to normal.

TobiDev_
Published at 8/26/2026
An unhandled error has occurred. Reload 🗙