Akamai Cloud (Linode) reported "Service Issue - Cloud Manager and API" on its status page at 2026-10-09 03:43 UTC.

Akamai Cloud (Linode) lists these components: Cloud Manager and API.

When did the incident start and end?

It started at 2026-10-09 03:43 UTC and ended at 2026-10-13 08:03 UTC. It lasted 4 days.

How do I get alerts for Akamai Cloud (Linode)?

Subscribe to the Akamai Cloud (Linode) live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Akamai Cloud (Linode). outages.live reads it every few minutes and keeps every update.

Akamai Cloud (Linode)Incident · 2026-10-09 03:43 UTC

Service Issue - Cloud Manager and API

ResolvedOfficial update

We haven't observed any additional issues with the Cloud Manager logins, and will now consider this incident resolved. If you continue to experience issues receiving verification codes, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

The latest update from Akamai Cloud (Linode).

State

Resolved

Started

23 d ago

2026-10-09 03:43 UTC

Lasted

4 days

until 2026-10-13 08:03 UTC

Worst impact

Degraded

Timeline

3 updates

Oct 9Oct 10Oct 11Oct 12Oct 13

DegradedUpdate postedDates in UTC

Identified

1 h 40 min 2%

Monitoring

4 days 98%

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Resolved2026-10-13 08:03 UTC

Monitoring2026-10-09 05:23 UTC

At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to receive verification codes please open a Support ticket , call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.

Identified2026-10-09 03:43 UTC

Our team has identified the issue affecting Cloud Manager logins, where customers may not receive verification codes in some scenarios. We are working quickly to implement a fix and will provide an update as soon as the solution is in place.

Affected components

Cloud Manager and API

Akamai Cloud (Linode) in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

6 h 29 min

This incident

15× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 days

median 6 h 29 min

90 days agoToday

Other Akamai Cloud (Linode) incidents

All incidents

Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)

A service issue affects US-Southeast (Atlanta). Akamai Cloud (Linode) reports that the region has degraded performance. Akamai Cloud (Linode) is still investigating the issue.

Degradedupdated 11 h ago

Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432

Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. Akamai states that it is investigating and is deploying mitigations for the known attack vector. Akamai advises customers to apply OS updates from their upstream provider when those updates become available.

Noticeupdated 1 d ago

Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)

Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud reports that a fix is in place and the state is monitoring.

Noticeupdated 3 d ago

Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)

Akamai Cloud reports a connectivity problem between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). The service is degraded in these two regions. Akamai Cloud moved the incident to monitoring and continues to monitor the impact.

Degradedupdated 3 d ago

Akamai Cloud (Linode)·Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)

This issue is considered resolved.

Resolvedresolved 8 d ago

Follow Akamai Cloud (Linode)

Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=linode

Slack

/feed subscribe https://outages.cc/feed.xml?providers=linode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane