Provider
LinodeIncident detail
Emerging Service Issue - API - All Regions
Timeline window
to
Outage alerts
Get alerted the next time Linode breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Linode posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
Our team is investigating an emerging service issue affecting the API in all regions. We will share additional updates as we have more information.
Monitoring
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 support@linode.com.
Monitoring
We are continuing to monitor for any further issues.
Resolved
This incident has been resolved.
Resolved
On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting _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 prevented it from absorbing the full traffic load after the failover. Engineers completed a controlled migration and moved request caching traffic back over to the primary host. Following this change, API latency rapidly decreased to normal operational levels.
The initial condition was triggered by an unexpected reboot of the primary caching node's physical host. While redundant infrastructure was active, the secondary node was unable to process the failover traffic seamlessly, causing the extended performance degradation.
Our engineering teams are conducting a follow-up investigation into the failover mechanisms to optimize execution speeds and align configuration settings across redundant nodes, ensuring secondary systems can handle traffic seamlessly in future events.
This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
Keep exploring
More from Linode
Neighboring incidents on Linode's timeline and the rest of their record on OutageDeck.