Pro-tip: Don't host your status / outage page on your own infrastructure. We learned this lesson the hard way at AWS with S3.
You just hang up cuz you know it’s everyone.
They don't even have a dedicated status/outage page, afaik.
The website being down is a more classic problem. The outage probably increased traffic to their website by 1000x if not more and the infrastructure for the website simply couldn't cope.
Good lesson on keeping your status infrastructure simple and on something which is highly scalable.
Having a CDN where the main page of their site was 99% cached globally would have probably mitigated this issue.
A problem in their network would take down the sites, and maybe the control plane for satellites.