I’ve updated the initial post with more information.
The website IPs 220.127.116.11 and 18.104.22.168 are still disabled. Some some websites will still be down.
Most other functions have been restored around 9:30 UTC for all other accounts, safe for another half hour outage at 15:00.
All the known symptoms are described in the initial post. If your website has an issue not covered in the list above, it might be unrelated. And to help make sure this thread stays on topic about the outage, please create a new topic and describe the problem there if you’re in doubt.
So @nirajkumarsinghit and @fuckinfinityfree, please create a separate topic and describe the issue there so we can help you effectively in a clean, on-point topic.
Just to clarify, you’re experiencing this issue if you have at least one of the symptoms, even if you don’t see all of them. After all, your website can’t simultaneously return a 502 error code and show a timeout error (indicating no response was sent by the server).
The thing with timeout error is that they are rendered by the web browser, not the server. So every browser will show a different error message and error code. And some browser may not provide any usable information at all.
In your case, one of your accounts is on one of the IPs which is currently down. So what you see is in fact related to this outage.