Emerging Host Issue
Akamai Cloud (Linode) reported degraded Linode migrations and booting for some hosts across all regions. Akamai Cloud (Linode) identified the issue and put a fix in place. The incident is resolved and lasted about 4 hours and 24 minutes.
State
Resolved
Started
Lasted
4 h 24 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 7 min 25%
Identified
3 h 17 min 75%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
We have implemented a fix, and after a period of monitoring, we can confirm that this incident is resolved as of 14:09 UTC on November 5, 2026. If you are still experiencing additional issues, please open a Support ticket for assistance.
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
30
Days with an incident
89
Median duration
5 h 8 min
This incident
About the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability
Akamai is aware of the password authentication bypass vulnerability affecting certain Linux systems using musl libc that was recently mitigated by an urgent OpenSSH update . Since Alpine Linux is specifically called out as being affected, we wanted to assure customers that Linode’s Alpine images are not affected by this vulnerability. Linodes using password-less provisioning do not have password authentication enabled by default unless customers change this configuration option in sshd_config after launch, while linodes launched using a password do not have any unlocked user accounts with a password hash set to ‘*’. However, we would like to use this opportunity as a reminder for customers to consider disabling password authentication permanently in favor of more secure mechanisms such as SSH keys or SSH CA certificates.
Akamai Cloud (Linode)·Connectivity Issue - FR-PAR-2 (Paris 2)
Connectivity does not work in the FR-PAR-2 (Paris 2) data center. Akamai Cloud (Linode) reports that it resolved the incident. The incident lasted about 2 hours and 50 minutes.
Akamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2
Connectivity does not work in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. The provider reports that the incident is resolved. The outage lasted about 3 hours and 12 minutes.
Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
A service issue affects US-Southeast (Atlanta) and Regions - US-Southeast (Atlanta). Akamai Cloud reports that the issue is resolved. The issue lasted from 31 October 2026 to 2 November 2026, about 48 hours.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432 that affects the Akamai Compute platform. Akamai Cloud (Linode) is investigating. Akamai Cloud (Linode) deployed network rules that drop IPv4 packets with optional headers on public and VPC interfaces. Customers should apply OS updates from their upstream provider when available.
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.cc/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.cc/feed.xml?providers=linode/feed subscribe https://outages.cc/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane