← Back to Linode (Akamai)'s check readings
We started checking Linode (Akamai) on August 22, 2026, which is 63 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Linode (Akamai) reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Linode (Akamai)'s own status page declared. Below it, any public chatter we saw about Linode (Akamai) and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Linode (Akamai)'s own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Linode (Akamai) in the last 24 hours, which is not evidence that nothing is wrong.
Linode (Akamai)'s status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Linode (Akamai)'s own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Linode (Akamai) next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Linode (Akamai)'s own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Customer Security Advisory: Critical F5/NGINX Out-of-Band VulnerabilitiesOngoing, all systems operational
Oct 22, 2026, 8:08 PM UTC, open for 2h 19m so farinvestigating
their latest update (Oct 22, 2026, 8:08 PM UTC): Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure.
F5 has released out-of-band security patches addressin…
Service Issue - Linode Kubernetes EngineAll systems operational
Oct 22, 2026, 1:58 PM UTC to Oct 22, 2026, 1:58 PM UTC (0 min)postmortem published
their latest update (Oct 22, 2026, 4:00 PM UTC): On October 22, 2026, starting around 11:10 UTC, a new Debian Kubernetes image was made available. The metadata for that image included malformed data, which resulted in Linode provisioning failures on LKE clusters due to validation errors.
Akamai immediately began investigating …
Customer Security Advisory: PHP Remote Code Execution VulnerabilitiesOngoing, all systems operational
Oct 21, 2026, 2:44 PM UTC, open for 1d 7h so faridentified
their latest update (Oct 22, 2026, 6:19 PM UTC): Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will…
Issue in creating new LKE Enterprise cluster across regionsMinor incident
Oct 20, 2026, 12:29 PM UTC to Oct 20, 2026, 9:42 PM UTC (9h 14m)postmortem published
their latest update (Oct 21, 2026, 3:49 PM UTC): Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully …
Connectivity Issue - US-ORDAll systems operational
Oct 19, 2026, 2:49 PM UTC to Oct 19, 2026, 8:33 PM UTC (5h 43m)resolved
their latest update (Oct 19, 2026, 8:33 PM UTC): 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]Ongoing, all systems operational
Oct 15, 2026, 5:27 PM UTC, open for 7d 5h so faridentified
their latest update (Oct 17, 2026, 5:07 AM UTC): Akamai has completed patching Compute hypervisors for the known vulnerabilities related to CVE-2026-99999, also referred to as “PwnEscape”, and we have not identified any exploitation on the Akamai platform.
We recommend that customers upgrade Linode guest VMs using kernels from…
Maintenance - Akamai Cloud Login ServiceMaintenance
Oct 15, 2026, 5:15 PM UTC to Oct 16, 2026, 12:20 PM UTC (19h 5m)resolved
their latest update (Oct 16, 2026, 12:20 PM UTC): The maintenance has been completed. New customer signup and account creation are fully restored.
Service Issue - Cloud Manager and APIMinor incident
Oct 9, 2026, 3:43 AM UTC to Oct 13, 2026, 8:03 AM UTC (4d 4h)resolved
their latest update (Oct 13, 2026, 8:03 AM UTC): We haven't observed any additional issues with the Cloud Manager logins, and will now consider this incident resolved. If you continue to experience issues receiving verification codes, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.…
Service Issue - Object Storage - US-Southeast (Atlanta)Minor incident
Oct 2, 2026, 4:01 PM UTC to Oct 2, 2026, 8:17 PM UTC (4h 16m)resolved
their latest update (Oct 2, 2026, 8:17 PM UTC): We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Service Issue - Cloud Manager and APIMinor incident
Sep 25, 2026, 3:09 PM UTC to Sep 25, 2026, 4:21 PM UTC (1h 12m)resolved
their latest update (Sep 25, 2026, 4:21 PM UTC): We haven't observed any additional issues with the Cloud Manager or API, 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 support@linode.com for assistance.
Showing the 10 most recent of 66 incidents Linode (Akamai) has declared in the history we hold.
These entries are Linode (Akamai)'s own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Linode (Akamai)'s own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.