Connectivity Issue - US-ORD
Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were adopted and converged at 14:55 UTC on October 19, 2026. To prevent this issue from reoccurring, we are modifying our maintenance planning process to ensure that critical components are taken offline in a phased manner that doesn’t introduce customer impact. 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.
The latest update from Akamai Cloud (Linode).
State
Resolved
Started
13 d ago
2026-10-19 14:49 UTC
Lasted
5 h 43 min
until 2026-10-19 20:33 UTC
Worst impact
Notice
Timeline
4 updatesInvestigating
39 min 11%
Monitoring
5 h 4 min 89%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were adopted and converged at 14:55 UTC on October 19, 2026. To prevent this issue from reoccurring, we are modifying our maintenance planning process to ensure that critical components are taken offline in a phased manner that doesn’t introduce customer impact. 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.
We haven’t observed any additional connectivity issues in our Chicago (US-ORD) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
At this time we have been able to correct the issues affecting connectivity in our Chicago (US-ORD) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Our team has identified an issue affecting connectivity in our Chicago (US-ORD) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.
Affected components
1Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
89
Median duration
5 h 43 min
This incident
About the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2
Connectivity does not work for services in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. Akamai Cloud reports that the incident is resolved. The outage lasted 3 hours and 12 minutes.
Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
Akamai Cloud (Linode) reports degraded service in the US-Southeast (Atlanta) region. The affected components are the US-Southeast (Atlanta) region and Regions - US-Southeast (Atlanta). Akamai Cloud is investigating the issue.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. The current state is investigating. Akamai advises customers to apply OS updates from their upstream provider as soon as those updates become available.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud (Linode) reports that a fix is in place and the provider monitors the result. The issue started on 28 October 2026.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Connectivity between the ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) regions is degraded. Akamai Cloud reports that monitoring is in progress. The start time was 25 October 2026.
Follow Akamai Cloud (Linode)
Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=linode/feed subscribe https://outages.live/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane