Network unreachable

Cases

1. IL-0354 Fly.io private networking (6PN) broke for some machines after edges received gateway /80 routesFly.io · 2026

   Root cause Faulty deployment

2. IL-0463 Secure Connect connectors timed out after a GKE control plane upgrade left Harness's internal load balancer unreachableHarness · 2026

   Root cause Cloud provider outage

3. IL-0400 Public sector sites across Wales lost connectivity for over 8 hours as a PE router wrongly advertised a default routePSBA · 2026

   Root cause Configuration change

4. IL-0350 Hosts in an IONOS TXL cluster lost connectivity when an InfiniBand fabric resweep failed on a full multicast tableIONOS Cloud · 2026

   Root cause Capacity exhaustion

5. IL-0349 IONOS Private Cloud in Berlin lost management access, storage and VM internet routing after a VLAN changeIONOS Cloud · 2026

   Root cause Operator error

6. IL-0368 PlanetScale's control plane went down and some database branches failed queries during the AWS us-east-1 outagePlanetScale · 2025

   Root cause Cloud provider outage

7. IL-0227 Most Heroku dynos in Private Spaces lost outbound connectivity after an automated OS update restarted host networkingHeroku · 2025

   Root cause Breaking change in an upgrade

8. IL-0563 Linode servers lost connectivity in all data centers as route servers built incomplete BGP route tablesLinode · 2025

   Root cause Faulty deployment

9. IL-0233 A VPC control plane release broke IP alias routes in Nebius eu-west1, and Managed Kubernetes pods lost connectivityNebius · 2025

   Root cause Software defect

10. IL-0526 OpenStreetMap.org went offline, then read-only, for 56 hours after HE.net routing equipment cut both fibre uplinksOpenStreetMap Foundation · 2024

    Root cause Dependency failure

11. IL-0347 About 25% of Scaleway FR-PAR-1 hypervisors lost VPC connectivity when both VPC BGP route reflectors got stuckScaleway · 2024

    Root cause Software defect

12. IL-0244 A queued pull request destroyed the EKS subnet route table associations and Cloud Platform services went offlineUK Ministry of Justice · 2024

    Root cause Operator error

13. IL-0423 A core switch failure in Paperspace's NY2 region cut VMs off their network file system and left them read-onlyPaperspace · 2024

    Root cause DNS or network fault

14. IL-0529 New Google Cloud VMs and other instances came up without network connectivity in all zones after VPC controllers stoppedGoogle Cloud · 2024

    Root cause Software defect

15. IL-0509 SourceHut was down for 170 hours after a DDoS led its upstream network to null-route the PHL datacenter's subnetSourceHut · 2024

    Root cause Dependency failure

16. IL-0530 Virtual router controllers in us-central1 ran out of memory in a loop, cutting networking for new and migrated VMsGoogle Cloud · 2023

    Root cause Faulty deployment

17. IL-0342 DigitalOcean's AMS3, LON1 and SFO2 data centers lost Internet connectivity in repeated waves as edge routers failedDigitalOcean · 2023

    Root cause Software defect

18. IL-0473 Jenkins infrastructure went fully down after a pod IP range fix deleted every AKS node pool and could not recreate themJenkins project · 2023

    Root cause Configuration change

19. IL-0259 Outbound packets from Fastmail did not reach part of the internet for about 19 hours, cutting off 3-5% of customersFastmail · 2023

    Root cause Dependency failure

20. IL-0541 Two Twingate Relay clusters were discoverable but unreachable, so Clients and Connectors could not attach to themTwingate · 2023

    Root cause Configuration change

21. IL-0344 Linode's US-West data centers in Fremont and Santa Clara lost connectivity as the fibre circuits between them failedLinode · 2023

    Root cause Software defect

22. IL-0225 An IGP purge command made every Microsoft WAN router recompute routes, causing global latency, timeouts and packet lossMicrosoft Azure · 2023

    Root cause Configuration change

23. 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

24. IL-0525 OpenStreetMap.org went offline for 7h 27m when its uplink switch lost power during a data-centre power feed maintenanceOpenStreetMap Foundation · 2022

    Root cause Hardware failure

25. IL-0266 Eqiad routers looped traffic between each other after a BGP MED change and could not reach other sites' public IPsWikimedia Foundation · 2021

    Root cause Configuration change

26. IL-0539 KT's internet service failed nationwide for about 89 minutes as wrong routes spread from one router in BusanKT · 2021

    Root cause Configuration change

27. IL-0228 IPv4 routing across OVHcloud's global network broke after a router change put the full internet routing table into OSPFOVHcloud · 2021

    Root cause Configuration change

28. IL-0221 A backbone maintenance command disconnected all Facebook data centers, and its DNS servers withdrew their BGP routesMeta · 2021

    Root cause Operator error

29. IL-0222 Google Cloud US regions had heavy packet loss and some went unreachable after the network control plane was descheduledGoogle Cloud · 2019

    Root cause Software defect

30. IL-0358 Packet Public Cloud locations had high latency and unreachable paths from routing loops and blackholed trafficPacket · 2019

    Root cause Dependency failure

31. IL-0245 Acquia Cloud Enterprise sites in US-East went down when their web servers could no longer reach the Memcache serversAcquia · 2019

    Root cause Operator error

32. IL-0472 Node-to-pod traffic and DNS failed on Tinder's 605-node Flannel cluster when every node's ARP cache passed gc_thresh3Tinder · 2019

    Root cause Capacity exhaustion

33. IL-0261 Discord went fully offline twice as short network losses on Google Cloud sessions nodes wedged Erlang distributionDiscord · 2017

    Root cause Cloud provider outage

34. IL-0431 During Mackerel's move to AWS, PostgreSQL failed over to a replica that had stopped replicating, losing an hour of dataHatena · 2017

    Root cause Operator error

35. IL-0396 New or live-migrated GCE instances, VPN tunnels and network load balancers were unreachable on public IPs for over 2hGoogle Cloud · 2017

    Root cause Software defect

36. IL-0494 Netlify's central load balancer IP stopped responding when Rackspace null-routed it in a DDoS, and A-record sites hungNetlify · 2016

    Root cause Cloud provider outage

37. IL-0519 Apps on the cloud.gov PaaS became unavailable after an AWS security group change blocked their outbound trafficcloud.gov · 2016

    Root cause Configuration change

38. IL-0258 FastMail was unreachable for almost two hours when the GRE tunnels carrying its traffic from Level 3 went downFastmail · 2016

    Root cause Dependency failure

39. IL-0337 EBS volumes in one US East Availability Zone got stuck after a network change cut EBS nodes off from their replicasAmazon Web Services · 2011

    Root cause Operator error