Interesting! Thanks for sharing this @lukakostic.
I was not able to replicate this on my machine. After jumping onto the same page(link) as yours, I turned my WiFi off to see if it gave me the same error, and it did not. It might have happened due to the ongoing maintenance but I'd like to know if it still gives you this error.

If it still happens, please share more information about your device and browser. I'd like to add an issue and share it with the devs if it does.