outages.live
Live
Akamai Cloud (Linode)Incident · 2026-10-25 13:54 UTC

Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)

DegradedOfficial update
0

Connectivity between the ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) regions is degraded. Akamai Cloud reports that monitoring is in progress. The start time was 25 October 2026.

State

Monitoring

Started

8 d ago

2026-10-25 13:54 UTC

Ongoing for

8 days

Worst impact

Degraded

Timeline

1 update
Oct 25Oct 27Oct 29Oct 31Nov 2
DegradedUpdate postedDates in UTC

Monitoring

8 days 100%

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Monitoring2026-11-01 08:39 UTC

We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.

Affected components

4
ID-CGK (Jakarta)SG-SIN-2 (Singapore 2)Regions - ID-CGK (Jakarta)Regions - SG-SIN-2 (Singapore 2)

Akamai Cloud (Linode) in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

28

Days with an incident

89

Median duration

5 h 43 min

This incident

31× the median

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

15 days
median 5 h 43 min
90 days agoToday

Other Akamai Cloud (Linode) incidents

All incidents

Akamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2

Connectivity does not work for services in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. Akamai Cloud reports that the incident is resolved. The outage lasted 3 hours and 12 minutes.

Resolvedresolved 6 h ago

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

Akamai Cloud (Linode) reports degraded service in the US-Southeast (Atlanta) region. The affected components are the US-Southeast (Atlanta) region and Regions - US-Southeast (Atlanta). Akamai Cloud is investigating the issue.

Degradedupdated 1 d ago

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

Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. The current state is investigating. Akamai advises customers to apply OS updates from their upstream provider as soon as those updates become available.

Noticeupdated 2 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 (Linode) reports that a fix is in place and the provider monitors the result. The issue started on 28 October 2026.

Noticeupdated 4 d ago

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

This issue is considered resolved.

Resolvedresolved 9 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.live/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.live/feed.xml?providers=linode
Slack
/feed subscribe https://outages.live/feed.xml?providers=linode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane