Incident Library
Applied filters SymptomPacket lossOrganisationLinodeClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

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

Cases1 case

1 to 1 of 1

  1. IL-0564 Linode's Miami, Milan and Sao Paulo data centers had packet loss as traffic moved onto congested alternate paths
    Linode2025
    Symptoms

    Customers using Linode's US-MIA (Miami) and IT-MIL (Milan) data centers saw packet loss and brief performance problems on 14 September 2025 from 17:42 to 18:43 UTC. BR-GRU (Sao Paulo) had the same packet loss on 15 September 2025 from 01:44 to 04:22 UTC.

    Packet loss
    Trigger

    A gradual increase in prefixes pushed the routing between the core router and the edge router past the maximum number of permitted prefixes.

    Root cause
    Capacity exhaustion
    Component
    BGP routingBackbone network (WAN)
    Contributing factor
    –
    Remediation
    • Raised the prefix limit on all the data center routers
    Action items
    • Raise the thresholds of the sessions between Akamai's backbone and the data center ECOR routers
    • Improve the existing alerting and check its severity before limits are reached, with escalation to the right team for immediate action
    View case
Check your cluster for this

This case involves Backbone network (WAN) and BGP routing. 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.

Open kubegap

By root cause1

Capacity exhaustion1 case

Component
Backbone network (WAN)BGP routing
Contributing factor
–
Organisation
Linode
  1. IL-0564 Linode's Miami, Milan and Sao Paulo data centers had packet loss as traffic moved onto congested alternate paths
    Linode2025