It seems like the issue might indeed be server-related, especially since multiple browsers show the same problem. Hopefully, the community team can resolve it soon, as it could be linked to the recent maintenance.