CDN and edge network

Cases, by severity

1. IL-0512 xpro.mit.edu returned 503 for an hour when its Kubernetes/APISIX origin certificate expired after renewal failedMIT Open Learning · 2026 · sev1

   Root cause Configuration change

2. IL-0515 Downloads from files.pythonhosted.org failed with intermittent 502 and 503 errors for two weeks, breaking PyPI installsPython Software Foundation · 2026

   Root cause Dependency failure

3. IL-0438 Builder Work became almost entirely unreachable with 504 errors when the Amazon CloudFront VPC Origins feature failedANDPAD · 2026

   Root cause Cloud provider outage

4. IL-0353 Fly.io edge proxies in US west coast regions were overloaded and flapping, with lazy loader delays of secondsFly.io · 2026

   Root cause Capacity exhaustion

5. IL-0283 Cloudflare's core proxy returned HTTP 5xx across its network after loading an oversized Bot Management feature fileCloudflare · 2025

   Root cause Configuration change

6. IL-0226 Azure Front Door edge servers crashed worldwide on incompatible configuration metadata, causing timeouts and DNS errorsMicrosoft Azure · 2025

   Root cause Software defect

7. IL-0357 Up to 22% of Vercel static file requests failed when part of its global cache was lost during the AWS us-east-1 outageVercel · 2025

   Root cause Cloud provider outage

8. IL-0341 Traffic between Cloudflare and AWS us-east-1 had high latency, packet loss and origin failures for almost four hoursCloudflare · 2025

   Root cause Capacity exhaustion

9. IL-0584 Cloud CDN at Osaka served corrupted JavaScript files, and a single-page app failed with a SyntaxError in western JapanMonicle · 2024

   Root cause Cloud provider outage

10. IL-0257 canva.com went down for about 50 minutes when 1.5 million requests per second OOM-killed every API Gateway taskCanva · 2024

    Root cause Dependency failure

11. IL-0555 Sentry's ingestion edge regions backlogged one after another and rejected traffic in three incidents in October 2024Sentry · 2024

    Root cause Capacity exhaustion

12. IL-0339 Azure Front Door and Azure CDN users saw intermittent connection errors, timeouts and latency spikes for hoursMicrosoft Azure · 2024

    Root cause Configuration change

13. IL-0363 static.crates.io did not resolve for 10-15 minutes during a Terraform deployment, so Rust builds could not fetch cratesRust Project · 2023

    Root cause Configuration change

14. IL-0267 Wikimedia's eqsin cache site went unreachable when both of its transport links to the core data centers were downWikimedia Foundation · 2023

    Root cause Dependency failure

15. IL-0522 An ingress-nginx chart upgrade deleted the jenkins.io Ingress and Fastly served HTTP/503 errors for hoursJenkins project · 2021

    Root cause Breaking change in an upgrade

16. IL-0229 bunny.net's DNS servers crashed in a loop on a corrupted routing database file and could not fetch a fix from its CDNbunny.net · 2021

    Root cause Faulty deployment

17. IL-0398 GOV.UK showed "Error 503 Service Unavailable" pages for under an hour during a global outage of its primary CDNGovernment Digital Service · 2021

    Root cause Dependency failure

18. IL-0491 Squarespace's CDN origin fleet fell below its healthy node threshold, and images, scripts and stylesheets failed to loadSquarespace · 2019

    Root cause Operator error

19. IL-0338 Google Cloud HTTP(S) and TCP/SSL Proxy load balancers returned 502s or reset connections on 33% to 87% of requestsGoogle Cloud · 2018

    Root cause Software defect

20. IL-0388 A Google Cloud live migration took a Discord Redis primary offline, and the failover broke API instances and then guildsDiscord · 2017

    Root cause Software defect