Skip to main content
down.guideby Sazabi
Providers
Is Akamai Cloud (Linode) down? · Cloud and CDN

Akamai Cloud (Linode) is up

OperationalNo known problems: Akamai Cloud (Linode)'s status page says operational

100.00% uptime, 90 days · 99.99% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Akamai Cloud (Linode) has posted and not resolved.

Akamai Cloud (Linode) has no open incidents.

Minor

Minor or regional issues (2)

Open issues confined to one country, region, site, carrier route, asset or slice of customers. Akamai Cloud (Linode)'s state, uptime and the Down Index leave them out.

  1. Akamai Cloud (Linode)OperationalMonitoring
    Service Issue - Block Storage (BR-GRU)
    monitoring a fix, open 13d 4hBR-GRU (São Paulo) Block Storagelatam
  2. Akamai Cloud (Linode)DegradedMonitoring
    Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
    monitoring a fix, open 16d 11hID-CGK (Jakarta), SG-SIN-2 (Singapore 2)apac
90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-14: 1 incident, worst degraded
  2. 2026-08-15: 1 incident, worst degraded
  3. 2026-08-16: 1 incident, worst degraded
  4. 2026-08-17: 1 incident, worst degraded
  5. 2026-08-18: 1 incident, worst degraded
  6. 2026-08-19: 1 incident, worst degraded
  7. 2026-08-20: 1 incident, worst degraded
  8. 2026-08-21: 1 incident, worst degraded
  9. 2026-08-22: 1 incident, worst degraded
  10. 2026-08-23: 1 incident, worst degraded
  11. 2026-08-24: 1 incident, worst degraded
  12. 2026-08-25: 1 incident, worst degraded
  13. 2026-08-26: 1 incident, worst degraded
  14. 2026-08-27: 1 incident, worst degraded
  15. 2026-08-28: 1 incident, worst degraded
  16. 2026-08-29: 1 incident, worst degraded
  17. 2026-08-30: 1 incident, worst degraded
  18. 2026-08-31: 1 incident, worst degraded
  19. 2026-09-01: 1 incident, worst degraded
  20. 2026-09-02: 1 incident, worst degraded
  21. 2026-09-03: 1 incident, worst degraded
  22. 2026-09-04: 1 incident, worst degraded
  23. 2026-09-05: 1 incident, worst degraded
  24. 2026-09-06: 1 incident, worst degraded
  25. 2026-09-07: 2 incidents, worst degraded
  26. 2026-09-08: 1 incident, worst degraded
  27. 2026-09-09: 1 incident, worst degraded
  28. 2026-09-10: 1 incident, worst degraded
  29. 2026-09-11: 1 incident, worst degraded
  30. 2026-09-12: 1 incident, worst degraded
  31. 2026-09-13: 1 incident, worst degraded
  32. 2026-09-14: 1 incident, worst degraded
  33. 2026-09-15: 1 incident, worst degraded
  34. 2026-09-16: 1 incident, worst degraded
  35. 2026-09-17: 1 incident, worst degraded
  36. 2026-09-18: 1 incident, worst degraded
  37. 2026-09-19: 1 incident, worst degraded
  38. 2026-09-20: 1 incident, worst degraded
  39. 2026-09-21: 2 incidents, worst degraded
  40. 2026-09-22: 2 incidents, worst degraded
  41. 2026-09-23: 2 incidents, worst degraded
  42. 2026-09-24: 1 incident, worst degraded
  43. 2026-09-25: 2 incidents, worst degraded
  44. 2026-09-26: 1 incident, worst degraded
  45. 2026-09-27: 1 incident, worst degraded
  46. 2026-09-28: 1 incident, worst degraded
  47. 2026-09-29: 1 incident, worst degraded
  48. 2026-09-30: 1 incident, worst degraded
  49. 2026-10-01: 1 incident, worst degraded
  50. 2026-10-02: 1 incident, worst degraded
  51. 2026-10-03: 1 incident, worst degraded
  52. 2026-10-04: 1 incident, worst degraded
  53. 2026-10-05: 1 incident, worst degraded
  54. 2026-10-06: 1 incident, worst degraded
  55. 2026-10-07: 1 incident, worst degraded
  56. 2026-10-08: 1 incident, worst degraded
  57. 2026-10-09: 1 incident, worst degraded
  58. 2026-10-10: 1 incident, worst degraded
  59. 2026-10-11: 1 incident, worst degraded
  60. 2026-10-12: 1 incident, worst degraded
  61. 2026-10-13: 1 incident, worst degraded
  62. 2026-10-14: no incidents
  63. 2026-10-15: no incidents
  64. 2026-10-16: no incidents
  65. 2026-10-17: no incidents
  66. 2026-10-18: no incidents
  67. 2026-10-19: no incidents
  68. 2026-10-20: 1 incident, worst degraded
  69. 2026-10-21: no incidents
  70. 2026-10-22: no incidents
  71. 2026-10-23: no incidents
  72. 2026-10-24: no incidents
  73. 2026-10-25: no incidents
  74. 2026-10-26: no incidents
  75. 2026-10-27: no incidents
  76. 2026-10-28: no incidents
  77. 2026-10-29: no incidents
  78. 2026-10-30: no incidents
  79. 2026-10-31: no incidents
  80. 2026-11-01: no incidents
  81. 2026-11-02: no incidents
  82. 2026-11-03: no incidents
  83. 2026-11-04: no incidents
  84. 2026-11-05: 1 incident, worst degraded
  85. 2026-11-06: no incidents
  86. 2026-11-07: no incidents
  87. 2026-11-08: no incidents
  88. 2026-11-09: no incidents
  89. 2026-11-10: no incidents
  90. 2026-11-11: no incidents
90 days agoToday

Daily history for the 12 components with the most incident days. Every component's current state is in the Markdown copy.

Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.99%12 months
Incidents
30on 63 days
Median duration
5h 8m
Longest
309d 6h
Postmortem rate
n/apartial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Akamai Cloud (Linode) incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=linode
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=linode in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=linode&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=linode&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

https://down.guide/api/v1/incidents?provider=linode
Open feed

Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.

History

Recent incidents

The last 90 days.

All history
  1. Akamai Cloud (Linode)Operational
    Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability [CVE-2026-123158]
    lasted 0mLinode.com
  2. Akamai Cloud (Linode)Degraded
    Emerging Host Issue
    lasted 4h 24mLinode.com
  3. Akamai Cloud (Linode)Degraded
    Connectivity Issue - FR-PAR-2 (Paris 2)
    lasted 2h 50mFR-PAR-2 (Paris 2)eu
  4. Akamai Cloud (Linode)Operational
    Connectivity Issue - IN-MAA and IN-BOM-2
    lasted 3h 12mIN-MAA (Chennai), IN-BOM-2 (Mumbai 2)apac
  5. Akamai Cloud (Linode)Operational
    Customer Security Advisory: CVE-2026-98432
    lasted 10d 3hCustomer Security Advisoryus
  6. Akamai Cloud (Linode)Operational
    Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
    lasted 11h 17mUS-Central (Dallas)us
  7. Akamai Cloud (Linode)Operational
    Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
    lasted 18d 21hCustomer Security Advisory
  8. Akamai Cloud (Linode)Operational
    Service Issue - Linode Kubernetes Engine
    lasted 0mUS-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine +28apac, au, ca, eu
  9. Akamai Cloud (Linode)Operational
    Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
    lasted 2d 5h
  10. Akamai Cloud (Linode)Degraded
    Issue in creating new LKE Enterprise cluster across regions
    lasted 9h 14mUS-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine +28apac, au, ca, eu
  11. Akamai Cloud (Linode)Operational
    Connectivity Issue - US-ORD
    lasted 5h 43mUS-ORD (Chicago)us
  12. Akamai Cloud (Linode)Operational
    (PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]
    lasted 14d 21hus
  13. Akamai Cloud (Linode)Maintenance
    Maintenance - Akamai Cloud Login Service
    lasted 19h 5mCloud Manager and API
  14. Akamai Cloud (Linode)Degraded
    Service Issue - Cloud Manager and API
    lasted 4d 4hCloud Manager and APIus
  15. Akamai Cloud (Linode)Degraded
    Service Issue - Object Storage - US-Southeast (Atlanta)
    lasted 4h 16mUS-Southeast (Atlanta) Object Storageus

Akamai Cloud (Linode) status: questions

Is Akamai Cloud (Linode) down right now?

No known problems: Akamai Cloud (Linode)'s status page says operational (checked 2026-11-11 01:12 UTC from Akamai Cloud (Linode)'s official status page).

What is Akamai Cloud (Linode)'s uptime?

100.00% over the last 90 days and 99.99% over 12 months, from the incidents Akamai Cloud (Linode) posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Akamai Cloud (Linode)'s last outage?

Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability [CVE-2026-123158], starting 2026-11-05 17:40 UTC and lasting 0m: https://down.guide/DWN-dd3637a877

How do I get alerts when Akamai Cloud (Linode) goes down?

Subscribe to https://down.guide/feed?provider=linode (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Akamai Cloud (Linode)'s status?

From Akamai Cloud (Linode)'s official status page, https://status.linode.com, read every minute. Akamai Cloud (Linode)'s words are quoted verbatim and linked.