Incident Library
  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases9 cases

9 to 9 of 9

  1. Symptoms

    At 4.50am Melbourne time on Sunday 7 February (evening of 6 February UTC), FastMail became unavailable and stayed unreachable for almost two hours. Traffic to FastMail's public IP range never made it into FastMail's own network.

    Trigger

    The GRE tunnels between Level 3 and NYI, which carried FastMail's filtered traffic into its network, went down.

    Root cause
    Component
    Contributing factor
    Detection

    NYI, the datacentre provider, noticed the failure quickly.

    Remediation
    • NYI escalated with Level 3's support until FastMail's public IP ranges were pointed back to NYI
    Action items
    • Go back to DDoS protection from Black Lotus under NYI's explicit control
    • Build nginx frontends in the Los Angeles datacentre that reach NYI over the secondary network, and point DNS to them if NYI's primary network fails
    • Add hardware in Amsterdam and change the delivery system so it depends less on NYI
    • Work with NYI to understand its processes for detecting and responding to network faults
    Lessons

    Much of FastMail's and NYI's reliability had come from NYI controlling its own infrastructure. With protection always on at Level 3, NYI could not restore the routes itself, and FastMail calls the resulting delay in restoring service unacceptable.

Check your cluster for this

These 9 cases involve BGP routing and Backbone network (WAN). kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause7

Configuration change1 case

Component
Organisation
  1. IL-0400 Public sector sites across Wales lost connectivity for over 8 hours as a PE router wrongly advertised a default route
    PSBA2026

Breaking change in an upgrade1 case

Organisation
  1. IL-0227 Most Heroku dynos in Private Spaces lost outbound connectivity after an automated OS update restarted host networking
    Heroku2025

Dependency failure2 cases

  1. IL-0509 SourceHut was down for 170 hours after a DDoS led its upstream network to null-route the PHL datacenter's subnet
  2. IL-0258 FastMail was unreachable for almost two hours when the GRE tunnels carrying its traffic from Level 3 went down

Hardware failure1 case

  1. IL-0525 OpenStreetMap.org went offline for 7h 27m when its uplink switch lost power during a data-centre power feed maintenance

Operator error1 case

Organisation
  1. IL-0221 A backbone maintenance command disconnected all Facebook data centers, and its DNS servers withdrew their BGP routes
    Meta2021

Software defect1 case

Organisation
  1. IL-0222 Google Cloud US regions had heavy packet loss and some went unreachable after the network control plane was descheduled

Cloud provider outage2 cases

Organisation
  1. IL-0261 Discord went fully offline twice as short network losses on Google Cloud sessions nodes wedged Erlang distribution
  2. IL-0494 Netlify's central load balancer IP stopped responding when Rackspace null-routed it in a DDoS, and A-record sites hung