Emerging Host Issue
Linode migrations and booting do not work for some hosts across all regions. Akamai Cloud (Linode) reports that the issue is identified and that a fix is in progress. The problem started 68 minutes ago.
State
Identified
Started
Ongoing for
1 h 9 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 8 min 99%
Identified
1 min 1%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
The issue affecting Linode migrations and booting for some hosts across all regions has been identified and a fix is being implemented. We will continue to share updates as more information becomes available.
We are currently investigating issues affecting Linode migrations and booting for some hosts across all regions. Our team is actively working on a resolution. 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
29
Days with an incident
89
Median duration
5 h 42 min
This incident
80% shorter than the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Connectivity Issue - FR-PAR-2 (Paris 2)
Connectivity does not work for services in the Akamai Cloud (Linode) FR-PAR-2 (Paris 2) data center. Users had intermittent connection timeouts and errors. Akamai Cloud (Linode) reports that the incident is resolved. The incident lasted about 2 hours and 50 minutes.
Akamai 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 a service issue that affects US-Southeast (Atlanta) and the Regions - US-Southeast (Atlanta) component. The problem is resolved. It lasted 2891 minutes.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432 on its Compute platform. Akamai Cloud is investigating and deploys kernel patches plus network rules that drop IPv4 packets with optional headers on public and VPC interfaces. Akamai Cloud advises customers to apply OS updates from their upstream provider as soon as those 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.
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