Skip to content

Outage tracker / Linode (Akamai)

Is Linode (Akamai) down?

Short linkrlup.io/down/linode

I'm having a problem

Operationalchecked 1 minute ago

We reached Linode (Akamai) from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Linode (Akamai) (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East355 msOperational
US-West811 msOperational
Europe665 msOperational
Asia-Pacific979 msOperational
US-Central835 msOperational
Canada916 msOperational
UK496 msOperational
Southeast Asia1053 msOperational
Australia1702 msOperational
South America2084 msOperational
their status pagetheir claim, not our reading

Linode (Akamai) reports: All systems operational (“All Systems Operational”)

from Linode (Akamai)'s own status page, checked Sep 5, 2026, 1:50 AM UTC
Our probes and Linode (Akamai)'s own status page agree: both show Linode (Akamai) as reachable right now.

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

US-East
677msp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 3.4s2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 951ms2026-08-28 UTC: p95 937ms2026-08-29 UTC: p95 851ms2026-08-30 UTC: p95 891ms2026-08-31 UTC: p95 829ms2026-09-01 UTC: p95 877ms2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 938ms2026-09-04 UTC: p95 829ms2026-09-05 UTC: p95 677ms
Aug 7Aug 21Sep 5
US-West
1.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 3.5s2026-08-23 UTC: p95 897ms2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 890ms2026-08-26 UTC: p95 815ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.6s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.5s2026-09-01 UTC: p95 976ms2026-09-02 UTC: p95 1.0s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.2s
Aug 7Aug 21Sep 5
Europe
933msp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 4.1s2026-08-23 UTC: p95 1.4s2026-08-24 UTC: p95 1.6s2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.5s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 933ms
Aug 7Aug 21Sep 5
Asia-Pacific
2.1sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 3.0s2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.7s2026-08-26 UTC: p95 1.6s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 1.7s2026-08-29 UTC: p95 1.6s2026-08-30 UTC: p95 1.9s2026-08-31 UTC: p95 1.8s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 1.7s2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.9s2026-09-05 UTC: p95 2.1s
Aug 7Aug 21Sep 5
US-Central
821msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 821ms
Aug 7Aug 21Sep 5
Canada
880msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 980ms2026-09-05 UTC: p95 880ms
Aug 7Aug 21Sep 5
UK
3.0sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 948ms2026-09-04 UTC: p95 834ms2026-09-05 UTC: p95 3.0s
Aug 7Aug 21Sep 5
Southeast Asia
1.5sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.7s2026-09-05 UTC: p95 1.5s
Aug 7Aug 21Sep 5
Australia
1.9sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 2.0s2026-09-05 UTC: p95 1.9s
Aug 7Aug 21Sep 5
South America
2.1sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.5s2026-09-04 UTC: p95 2.1s2026-09-05 UTC: p95 2.1s
Aug 7Aug 21Sep 5

Is it Linode (Akamai), or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 355msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 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-West
      Operationallatency: 811msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
      0 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-Central
      Operationallatency: 835msstatus code: 200checked: Sep 5, 2026, 2:04 AM UTC
      0 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.
    • Canada
      Operationallatency: 916msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 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 America
    Operationallatency: 2084msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 665msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC
      0 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.
    • UK
      Operationallatency: 496msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 979msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 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 Asia
      Operationallatency: 1053msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC
      0 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.
    • Australia
      Operationallatency: 1702msstatus code: 200checked: Sep 5, 2026, 1:51 AM UTC
      0 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 outages

Service Issue - US-SEA (Seattle, WA), 7h 18mdeclared on their status page2026-08-28
Service Issue - Object Storage - US-SEA, 3h 18mdeclared on their status page2026-08-24
Service Issue - US-SEA (Seattle, WA), 4h 36mdeclared on their status page2026-08-21
Connectivity Issue - IT-MIL (Milan) data center, 1h 17mdeclared on their status page2026-08-14
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Seattle (SEA1), 1mdeclared on their status page2026-08-14
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington), 2h 12mdeclared on their status page2026-08-13
Emerging Service Issue - API - All Regions, 5h 40mdeclared on their status page2026-08-13
Service Issue - Linode Kubernetes Engine (IAD2), 1h 38mdeclared on their status page2026-08-13

measured 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 measurements and Linode (Akamai)'s own claim at the time, side by side.

Full availability history for Linode (Akamai): 90-day availability by region, month-by-month uptime, and every incident 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 servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Linode (Akamai), and again when they can reach it again. That is our own measurement from ten regions, not Linode (Akamai)'s status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Linode (Akamai) uptime measured by RealUptimeLive, from this page's own readings.
[![Linode (Akamai) uptime measured by RealUptime](https://realuptime.io/outages/linode/badge.svg?days=30)](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Linode (Akamai)'s SLA implies, from our measurement

At or above your target

We measured none of downtime for Linode (Akamai) over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Linode (Akamai)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.linode.com/v4/regions
secondary
https://www.linode.com/
secondary
https://status.linode.com/api/v2/status.json
RealUptime is not affiliated with Linode (Akamai); the name identifies what we measured, and nothing here speaks for Linode (Akamai)'s own team. We send a single web request to Linode (Akamai) from 10 regions on our own schedule and time the response. We do not see inside Linode (Akamai)'s systems, do not use an account or real transaction, and are not the same signal Linode (Akamai)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Linode (Akamai) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)