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

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.

A language model wrote this summary from the updates of Akamai Cloud (Linode).

State

Monitoring

Started

7 d ago

2026-10-25 13:54 UTC

Ongoing for

7 days

Worst impact

Degraded

Timeline

1 update
Oct 25Oct 27Oct 28Oct 30Nov 1
DegradedUpdate postedDates in UTC

Monitoring

7 days 100%

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Monitoring2026-10-31 21:45 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

5

Days with an incident

11

Median duration

Not enough data

This incident

Not comparable

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

9 days
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 8 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)·Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

F5/NGINX out-of-band vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479 may affect Akamai Cloud (Linode) platform and infrastructure components. Akamai Cloud (Linode) reports that it is investigating the potential impact. F5 released patches. Akamai Cloud (Linode) recommends that customers who run a vulnerable NGINX Open Source or NGINX Plus version on a Linode instance apply the available patches.

Noticeupdated 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.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