← Back to Linode (Akamai)'s live status
We started measuring Linode (Akamai) on August 22, 2026, which is 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me the next time we see Linode (Akamai) go down
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 probe 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 probe is not an outage. Report bars count unverified reports, not people we verified; 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
Availability by region
Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
03
Monthly summary
Tracking Linode (Akamai) since Aug 22, 2026. In that time our probes detected 3 outages, 22h 29m in total. Months before that date are not tracked and carry no figure.
Uptime here is the share of each month in which our probes had no outage open for Linode (Akamai): two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Linode (Akamai)'s own status page contribute nothing to these figures.
04
Our incident log
Every outage our own probes detected for Linode (Akamai) in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Linode (Akamai)'s own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.
Sep 21, 2026, 4:59 AM UTC to Sep 22, 2026, 2:40 AM UTC21h 40m
multiple regions
Australia: failing from Sep 21, 2026, 4:01 PM UTC, recovered Sep 21, 2026, 5:21 PM UTCSouth America: failing from Sep 21, 2026, 4:59 AM UTC, recovered Sep 22, 2026, 2:40 AM UTC
Sep 7, 2026, 11:58 AM UTC to Sep 7, 2026, 12:08 PM UTC10 min
single region
Europe: failing from Sep 7, 2026, 11:58 AM UTC, recovered Sep 7, 2026, 12:08 PM UTC
Sep 7, 2026, 10:48 AM UTC to Sep 7, 2026, 11:27 AM UTC39 min
multiple regions
US-East: failing from Sep 7, 2026, 11:07 AM UTC, recovered Sep 7, 2026, 11:17 AM UTCUS-West: failing from Sep 7, 2026, 11:07 AM UTC, recovered Sep 7, 2026, 11:27 AM UTCEurope: failing from Sep 7, 2026, 10:48 AM UTC, recovered Sep 7, 2026, 11:08 AM UTC
Permanent incident records
Every closed Linode (Akamai) incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.
Their declared record
Linode (Akamai)'s own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.
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.
Emerging Service Issue - Cloud Manager and APIMinor incident
Sep 21, 2026, 5:13 PM UTC to Sep 23, 2026, 3:26 AM UTC (1d 10h)resolved
their latest update (Sep 23, 2026, 3:26 AM 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.
Emerging Service Issue - [DNS] - [eu-west]All systems operational
Sep 21, 2026, 4:50 PM UTC to Sep 22, 2026, 12:04 AM UTC (7h 15m)postmortem published
their latest update (Sep 24, 2026, 5:45 PM UTC): On September 21, 2026, starting at approximately 16:10 UTC, Akamai observed degraded DNS resolution performance affecting a subset of Linode instances within the London \(`LON1`\) region. Platform-wide DNS resolution remained functional, and no other regions were affected.
The d…
Service Issue - Cloud Manager and APIMinor incident
Sep 7, 2026, 10:38 AM UTC to Sep 7, 2026, 1:31 PM UTC (2h 53m)postmortem published
their latest update (Sep 8, 2026, 9:26 AM UTC): Between approximately 10:15 and 12:18 UTC on September 7, 2026, customers could have experienced elevated error rates and 5xx response codes when using Cloud Manager or performing API calls.
The investigation revealed that the issue started due to increased API load that over-u…
Service Issue - US-SEA (Seattle, WA)All systems operational
Aug 28, 2026, 10:26 AM UTC to Aug 28, 2026, 5:44 PM UTC (7h 18m)postmortem published
their latest update (Aug 28, 2026, 8:36 PM UTC): Between approximately 09:51 and 12:18 UTC on August 28, 2028, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected.
The investigation revealed that this was due to a Linux …
Service Issue - Object Storage - US-SEAAll systems operational
Aug 24, 2026, 9:52 PM UTC to Aug 25, 2026, 1:11 AM UTC (3h 18m)resolved
their latest update (Aug 25, 2026, 1:11 AM 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 - US-SEA (Seattle, WA)All systems operational
Aug 21, 2026, 5:23 PM UTC to Aug 21, 2026, 9:59 PM UTC (4h 36m)postmortem published
their latest update (Sep 7, 2026, 6:36 PM UTC): On August 21, 2026 starting approximately at 17:23 UTC, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected.
The investigation revealed that this was due to a Linux kernel…
Connectivity Issue - IT-MIL (Milan) data centerMinor incident
Aug 14, 2026, 8:13 PM UTC to Aug 14, 2026, 9:30 PM UTC (1h 17m)postmortem published
their latest update (Aug 18, 2026, 7:02 PM UTC): On August 14, 2026, starting around 17:30 UTC, during an event in our IT-MIL \(Milan\) data center, multiple alerts were triggered indicating that multiple hosts in this data center became unreachable.
Akamai immediately began investigating the issue and working to restore th…
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Seattle (SEA1)All systems operational
Aug 14, 2026, 3:46 PM UTC to Aug 13, 2026, 2:00 PM UTC (0 min)postmortem published
their latest update (Aug 21, 2026, 1:13 PM UTC): On August 13, 2026, between approximately 14:30 and 16:30 UTC, Akamai experienced an issue affecting Linode Kubernetes Engine Enterprise \(LKE-E\) cluster provisioning and deployment in the Seattle \(SEA1\) region. During this time, customers attempting to create new clusters enc…
Showing the 10 most recent of 57 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 the outages we detected ourselves. 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.
The scorecard
How Linode (Akamai)'s status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.
We started recording Linode (Akamai)'s own status page on August 22, 2026, 43 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.
outages compared: 3their status page reported a problem during 1 of 3reported operational while we measured down: 12h 28m in total
Sep 21, 2026, 4:59 AM UTC to Sep 22, 2026, 2:40 AM UTCTheir status page updated during the outage
multiple regions
Linode (Akamai)'s status page reported all systems operational for 12h 15m of this outage, then reported a problem for the remaining 9h 25m we measured.
South America: measured down 21h 40m; Linode (Akamai) reported operational for 12h 15m of it; they reported a problem for 9h 25m of it.Australia: measured down 1h 21m; Linode (Akamai) reported operational for 1h 13m of it; they reported a problem for 7 minutes of it.
Sep 7, 2026, 11:58 AM UTC to Sep 7, 2026, 12:08 PM UTCTheir status page agreed
single region
We measured Linode (Akamai) down in one of our regions (Europe), and Linode (Akamai)'s own status page reported a problem throughout. The two records agree.
Europe: measured down 10 minutes; they reported a problem for 10 minutes of it.
Sep 7, 2026, 10:48 AM UTC to Sep 7, 2026, 11:27 AM UTCTheir status page updated during the outage
multiple regions
Linode (Akamai)'s status page reported all systems operational for 13 minutes of this outage, then reported a problem for the remaining 25 minutes we measured.
Europe: measured down 20 minutes; Linode (Akamai) reported operational for 13 minutes of it; they reported a problem for 7 minutes of it.US-East: measured down 10 minutes; they reported a problem for 10 minutes of it.US-West: measured down 20 minutes; they reported a problem for 20 minutes of it.
Linode (Akamai) decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Linode (Akamai) believes a figure here is wrong, we publish corrections as prominently as the original.
Full detail on what a probe does and does not prove is in the methodology page.