Is Linode (Akamai) down?
Vendor reports an incident, no impactWhat Linode (Akamai) reports
Linode (Akamai) reports an incident on its status page: Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities.
Impact: no impact. Since 2026-10-22 20:08 UTC.
Latest update, 2026-10-22 20:08 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 addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed. If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches. We will provide updates as additional information becomes available.
One more incident is open on its status page.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked moments ago
Our checks of Linode (Akamai) pass from all 10 regions we check.
As of Oct 22, 2026, 9:51 PM UTC, RealUptime's checks of Linode (Akamai) passed in all 10 regions that returned a reading.
Linode (Akamai) reports: All systems operational (“All Systems Operational”)
Linode (Akamai) reports an active incident: Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities (all systems operational, since Oct 22, 2026, 8:08 PM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.
Linode (Akamai)'s own component breakdown, as they publish it
- Akamai Cloud Pulse (ACLP) - AlertsOperational
- Linode.comOperational
- US-East (Newark)Operational
- US-East (Newark)Operational
- US-East (Newark) BackupsOperational
- US-East (Newark) Block StorageOperational
- US-East (Newark) Linode Kubernetes EngineOperational
- US-East (Newark) NodeBalancersOperational
- US-East (Newark) Object StorageOperational
- Akamai Cloud Pulse (ACLP) - LogsOperational
- Cloud Manager and APIOperational
- US-Central (Dallas)Operational
- US-Central (Dallas)Operational
- US-Central (Dallas) BackupsOperational
- US-Central (Dallas) Block StorageOperational
- US-Central (Dallas) Linode Kubernetes EngineOperational
- US-Central (Dallas) NodeBalancersOperational
- US-Southeast (Atlanta) Object StorageOperational
- Akamai Cloud Pulse (ACLP) - MetricsOperational
- Hosted DNS ServiceOperational
- US-IAD (Washington) Object StorageOperational
- US-West (Fremont)Operational
- US-West (Fremont)Operational
- US-West (Fremont) BackupsOperational
- US-West (Fremont) Block StorageOperational
- US-West (Fremont) Linode Kubernetes EngineOperational
- US-West (Fremont) NodeBalancersOperational
- LongviewOperational
- US-ORD (Chicago) Object StorageOperational
- US-Southeast (Atlanta)Operational
- US-Southeast (Atlanta)Operational
- US-Southeast (Atlanta) BackupsOperational
- US-Southeast (Atlanta) Block StorageOperational
- US-Southeast (Atlanta) Linode Kubernetes EngineOperational
- US-Southeast (Atlanta) NodeBalancersOperational
- EU-Central (Frankfurt) Object StorageOperational
- Managed DatabasesOperational
- US-IAD (Washington)Operational
- US-IAD (Washington)Operational
- US-IAD (Washington) BackupsOperational
- US-IAD (Washington) Block StorageOperational
- US-IAD (Washington) Linode Kubernetes EngineOperational
- US-IAD (Washington) NodeBalancersOperational
- AP-South (Singapore) Object StorageOperational
- US-ORD (Chicago)Operational
- US-ORD (Chicago)Operational
- US-ORD (Chicago) BackupsOperational
- US-ORD (Chicago) Block StorageOperational
- US-ORD (Chicago) Linode Kubernetes EngineOperational
- US-ORD (Chicago) NodeBalancersOperational
- CA-Central (Toronto)Operational
- CA-Central (Toronto)Operational
- CA-Central (Toronto) BackupsOperational
- CA-Central (Toronto) Block StorageOperational
- CA-Central (Toronto) Linode Kubernetes EngineOperational
- CA-Central (Toronto) NodeBalancersOperational
- FR-PAR (Paris) Object StorageOperational
- EU-West (London)Operational
- EU-West (London)Operational
- EU-West (London) BackupsOperational
- EU-West (London) Block StorageOperational
- EU-West (London) Linode Kubernetes EngineOperational
- EU-West (London) NodeBalancersOperational
- SE-STO (Stockholm) Object StorageOperational
- EU-Central (Frankfurt)Operational
- EU-Central (Frankfurt)Operational
- EU-Central (Frankfurt) NodeBalancersOperational
- EU-Central (Frankfurt) BackupsOperational
- EU-Central (Frankfurt) Block StorageOperational
- EU-Central (Frankfurt) Linode Kubernetes EngineOperational
- US-SEA (Seattle) Object StorageOperational
- FR-PAR (Paris)Operational
- FR-PAR (Paris)Operational
- FR-PAR (Paris) BackupsOperational
- FR-PAR (Paris) Block StorageOperational
- FR-PAR (Paris) Linode Kubernetes EngineOperational
- FR-PAR (Paris) NodeBalancersOperational
- JP-OSA (Osaka) Object StorageOperational
- AP-South (Singapore)Operational
- AP-South (Singapore)Operational
- AP-South (Singapore) BackupsOperational
- AP-South (Singapore) Block StorageOperational
- AP-South (Singapore) Linode Kubernetes EngineOperational
- AP-South (Singapore) NodeBalancersOperational
- IN-MAA (Chennai) Object StorageOperational
- AP-Northeast (Tokyo 2) Linode Kubernetes EngineOperational
- AP-Northeast-2 (Tokyo 2)Operational
- AP-Northeast-2 (Tokyo 2)Operational
- AP-Northeast-2 (Tokyo 2) BackupsOperational
- AP-Northeast-2 (Tokyo 2) Block StorageOperational
- AP-Northeast-2 (Tokyo 2) NodeBalancersOperational
- ID-CGK (Jakarta) Object StorageOperational
- AP-West (Mumbai)Operational
- AP-West (Mumbai)Operational
- AP-West (Mumbai) BackupsOperational
- AP-West (Mumbai) Block StorageOperational
- AP-West (Mumbai) Linode Kubernetes EngineOperational
- AP-West (Mumbai) NodeBalancersOperational
- BR-GRU (Sao Paulo) Object StorageOperational
- AP-Southeast (Sydney)Operational
These are Linode (Akamai)'s components, named and scored by Linode (Akamai). We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Linode (Akamai)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Linode (Akamai) response time, by region
Check your own site while you wait on Linode (Akamai)
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Linode (Akamai). It cannot diagnose Linode (Akamai)'s own systems.
What we measured, function by function
Linode (Akamai) answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Linode (Akamai) reports an incident on its status page, and again when it reports it resolved.
Get an email when Linode (Akamai) reports an incident
Email me when Linode (Akamai) reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1087msstatus code: 200checked: Oct 22, 2026, 9:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Linode (Akamai) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1418msstatus code: 200checked: Oct 22, 2026, 9:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Linode (Akamai) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 828msstatus code: 200checked: Oct 22, 2026, 9:50 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Linode (Akamai) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 459msstatus code: 200checked: Oct 22, 2026, 9:50 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Linode (Akamai) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 2065msstatus code: 200checked: Oct 22, 2026, 9:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Linode (Akamai) normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 607msstatus code: 200checked: Oct 22, 2026, 9:42 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Linode (Akamai) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 733msstatus code: 200checked: Oct 22, 2026, 9:51 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Linode (Akamai) normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1335msstatus code: 200checked: Oct 22, 2026, 9:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Linode (Akamai) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1471msstatus code: 200checked: Oct 22, 2026, 9:39 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Linode (Akamai) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1546msstatus code: 200checked: Oct 22, 2026, 9:50 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Linode (Akamai) normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Linode (Akamai), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Linode (Akamai) yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Linode (Akamai) since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Linode (Akamai) covering any window you pick, with our check readings and Linode (Akamai)'s own claim at the time, side by side.
Full check history for Linode (Akamai): 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/linode)<a href="https://realuptime.io/outages/linode"><img src="https://realuptime.io/outages/linode/badge.svg?days=30" alt="Linode (Akamai) uptime by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is Linode (Akamai) down?", https://realuptime.io/outages/linode. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: api.linode.com