4 ms·
We don’t know. Suspect it may just have been a big uptick in load and a failure of its underlying infrastructure to scale up.
by eastdakota 11mo ago
We don’t know. Suspect it may just have been a big uptick in load and a failure of its underlying infrastructure to scale up.
- dnw 11mo agoYes, probably a bunch of automated bots decided to check the status page when they saw failures in production.
- reassess_blind 11mo agoThe status page is hosted on AWS Cloudfront, right? It sure looks like Cloudfront was overwhelmed by the traffic spike, which is a bit concerning. Hope we'll see a post from their side.
- gempir 11mo agoCloudFront has quotas[0] and they likely just hit those quota limits. To request higher quotas requires a service ticket. If they have access logs enabled in CloudFront they could see what the exact error was. And since it seems this is hosted by Atlassian, this would be up to Atlassian. [0] https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-limits.html#limits-general https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...
- jbmsf 11mo agoIt looks a lot like a CloudFront error we randomly saw today from one of our engineers in South America. I suspect there was a small outage in AWS but can't prove it.
- dilyevsky 11mo agoProbably non zero number of companies use cloudfront and other cdns as fallback for cloudflare or running a blended cdn so not surprising to see other cdns hit with a thundering herd when cloudflare went down
- francisofascii 11mo agoThis situation reminds me of risk assessment, where you sometimes assume two rare events are independent, but later learn they are actually highly correlated.