← Live dashboard

Emerging Service Issue - API - All Regions

ResolvedminorOfficial source confirmedGlobal service disruptionFirst recorded update Aug 13, 2026, 06:46 PM · Resolved Aug 14, 2026, 12:26 AM

On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting [_api.linode.com_](http://api.linode.com). The total service interruption lasted for approximately 3 minutes, concluding at 18:18 UTC. Following the restoration of initial connectivity, elevated API response latency persisted through 19:06 UTC, causing slower response times and intermittent delays for customers interacting with API services. To address the performance impact, Akamai engineering teams identified a configuration discrepancy on the secondary caching infrastructure node that...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

FR-PAR (Paris)US-East (Newark)US-Central (Dallas)US-West (Fremont)US-Southeast (Atlanta)US-IAD (Washington)US-ORD (Chicago)CA-Central (Toronto)EU-West (London)EU-Central (Frankfurt)AP-South (Singapore)AP-Northeast-2 (Tokyo 2)AP-West (Mumbai)AP-Southeast (Sydney)SE-STO (Stockholm)US-SEA (Seattle)IT-MIL (Milan)JP-OSA (Osaka)IN-MAA (Chennai)ID-CGK (Jakarta)BR-GRU (São Paulo)NL-AMS (Amsterdam)US-MIA (Miami)US-LAX (Los Angeles)ES-MAD (Madrid)AU-MEL (Melbourne)GB-LON (London 2)IN-BOM-2 (Mumbai 2)SG-SIN-2 (Singapore 2)DE-FRA-2 (Frankfurt 2)JP-TYO-3 (Tokyo 3)ZA-JNB (Johannesburg)NZ-AKL (Auckland)CO-BOG (Bogota)US-DEN (Denver)DE-HAM (Hamburg)US-HOU (Houston)MY-KUL (Kuala Lumpur)FR-MRS (Marseille)MX-QRO (Queretaro)CL-SCL (Santiago)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)Cloud Manager and API

Updates (5)

  1. Aug 17, 2026, 05:38 PM
    Emerging Service Issue - API - All Regions

    On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting [_api.linode.com_](http://api.linode.com). The total service interruption lasted for approximately 3 minutes, concluding at 18:18 UTC. Following the restoration of initial connectivity, elevated API response latency persisted through 19:06 UTC, causing slower response times and intermittent delays for customers interacting with API services. To address the performance impact, Akamai engineering teams identified a configuration discrepancy on the secondary caching infrastructure node that prevent

    Linode ↗
  2. Aug 14, 2026, 12:26 AM
    Emerging Service Issue - API - All Regions

    This incident has been resolved.

    Linode ↗
  3. Aug 13, 2026, 07:59 PM
    Emerging Service Issue - API - All Regions

    We are continuing to monitor for any further issues.

    Linode ↗
  4. Aug 13, 2026, 07:58 PM
    Emerging Service Issue - API - All Regions

    As of 19:30 UTC have been able to correct the issue affecting API in all regions. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

    Linode ↗
  5. Aug 13, 2026, 06:46 PM
    Emerging Service Issue - API - All Regions

    Our team is investigating an emerging service issue affecting the API in all regions. We will share additional updates as we have more information.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.