Linode/Akamai Status

Official pageUpdated
Degraded
Some systems are experiencing degraded performance.
Issue in creating new LKE Enterprise cluster across regions.
identified · Started · Minor impact
View incident →
(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]
identified · Started · Advisory
View incident →

System status

View historical uptime →
US-East (Newark) Block Storage
Linode.com
US-East (Newark)
US-East (Newark) NodeBalancers
US-East (Newark) Linode Kubernetes Engine
US-East (Newark)
Akamai Cloud Pulse (ACLP) - Alerts
US-East (Newark) Backups
US-East (Newark) Object Storage
US-Central (Dallas)
Akamai Cloud Pulse (ACLP) - Logs
US-Central (Dallas) NodeBalancers
US-Southeast (Atlanta) Object Storage
US-Central (Dallas)
US-Central (Dallas) Linode Kubernetes Engine
US-Central (Dallas) Backups
US-Central (Dallas) Block Storage
Cloud Manager and API
US-West (Fremont) Backups
US-West (Fremont)
US-West (Fremont) Linode Kubernetes Engine
US-West (Fremont) Block Storage
US-West (Fremont) NodeBalancers
US-IAD (Washington) Object Storage
US-West (Fremont)
1–25 of 250 components

Incident overview

Total incidents

21

Active now

2

Resolved

19

Avg. resolution

32h 41m

Recent incidents

View all →

Connectivity Issue - US-ORD

none

Maintenance - Akamai Cloud Login Service

maintenance

Service Issue - Cloud Manager and API

minor

Service Issue - Object Storage - US-Southeast (Atlanta)

minor

Service Issue - Cloud Manager and API

minor

Emerging Service Issue - Cloud Manager and API

minor

Emerging Service Issue - [DNS] - [eu-west]

none

Service Issue - Cloud Manager and API

minor

Service Issue - US-SEA (Seattle, WA)

none

Service Issue - Object Storage - US-SEA

none

Frequently asked questions

Is Linode/Akamai down right now?

Linode/Akamai is currently experiencing issues with 2 active incidents. Current status: Degraded. Check the incident details above for more information.

What is Linode/Akamai's current uptime?

Uptime data for Linode/Akamai is still being collected. DevHelm needs sufficient monitoring data before reporting uptime percentages. Check back soon.

How many incidents has Linode/Akamai had recently?

Linode/Akamai has experienced 21 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 32h 41m. 2 incidents are currently active.

What components does Linode/Akamai monitor?

DevHelm tracks 242 individual components for Linode/Akamai, including US-East (Newark) Backups, US-East (Newark) Block Storage, US-East (Newark), Akamai Cloud Pulse (ACLP) - Alerts, Linode.com, and 237 more. Each component has its own status and 90-day uptime history shown above.

How can I get notified about Linode/Akamai outages?

You can subscribe to Linode/Akamai's incident feed via Atom/RSS at devhelm.io/status/linode/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Linode/Akamai as a dependency in your DevHelm workspace.

What SLA does Linode/Akamai offer?

See the full Linode/Akamai SLA report at devhelm.io/sla/linode — including their official uptime guarantee, pricing tiers, credit policy, and how their measured uptime compares to their SLA commitment.

About Linode/Akamai status monitoring

This page provides real-time operational status for Linode/Akamai, powered by DevHelm's continuous monitoring infrastructure. We track Linode/Akamai's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.

Linode/Akamai status data is refreshed every 30 seconds. We currently track 242 individual components, each with its own operational status and 90-day uptime history.

Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.

Track Linode/Akamai in your stack

Get alerted when Linode/Akamai has issues — before your users notice. Set up in 30 seconds.

Start Free →