Comment by the_biot
8 hours ago
You have to wonder why it's so hard to put that on their 503 error page. I suspect something's much more broken than they're letting on.
8 hours ago
You have to wonder why it's so hard to put that on their 503 error page. I suspect something's much more broken than they're letting on.
This would indicate wherever they were hosting their site on no longer exists. 503's even on pages that should mostly be static suggest the backend no longer exists, or whatever ingress they're using in front of it disappeared. As far as I can tell every single page on their site is 503'ing.
Example of a response I see:
< x-cache: Error from cloudfront < via: 1.1 bdf85d6d4811ab08c57841855a848f8a.cloudfront.net (CloudFront) < x-amz-cf-pop: LAX54-P11 < x-amz-cf-id: nTQ-y1Ut3F-04jUCDM09ordCtj0CMkVmmtZTe__BtzEr1sMJu7rKaw== < age: 76773