Always fun when the status page goes down with the thing it's supposed to be reporting on. This is why your monitoring stack can't live on the same infrastructure it's watching. If your alerting depends on CloudFront and CloudFront is what's broken, you find out about the outage the same way your customers do: Twitter.

Status pages hosted by Atlassian's statuspage service are among the affected resources by this, which is always fun.

e.g. https://status.atlassian.com/

I just spent the last 20 minutes trying to debug why my non-www URL wasn't working and my www was. Oh well now I know.