GlobalOutageMap
← Live dashboard
Linode logoLinode

Service Issue - Linode API/CLI

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Jul 14, 2026, 12:21 PM · Resolved Jul 14, 2026, 07:26 PM

On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted.  Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by...

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

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

Updates (7)

  1. Jul 16, 2026, 06:13 PM
    Service Issue - Linode API/CLI

    On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted.  Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by a w

    Linode ↗
  2. Jul 14, 2026, 07:26 PM
    Service Issue - Linode API/CLI

    We haven't observed any additional issues with the Cloud Manager, API, or CLI, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

    Linode ↗
  3. Jul 14, 2026, 06:36 PM
    Service Issue - Linode API/CLI

    We are continuing to monitor for any further issues.

    Linode ↗
  4. Jul 14, 2026, 04:06 PM
    Service Issue - Linode API/CLI

    We are continuing to monitor for any further issues.

    Linode ↗
  5. Jul 14, 2026, 01:11 PM
    Service Issue - Linode API/CLI

    At this time we have been able to correct the issue affecting the Cloud Manager and API. 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 ↗
  6. Jul 14, 2026, 12:58 PM
    Service Issue - Linode API/CLI

    Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    Linode ↗
  7. Jul 14, 2026, 12:21 PM
    Service Issue - Linode API/CLI

    Our team is investigating an emerging service issue affecting the API and CLI. 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.