- Level
- confirmed
- Worst impact
- Major outage
- Components
- ID-CGK (Jakarta), AU-MEL (Melbourne) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine
- Regions
- apac, au
What to do
Check whether you use Akamai Cloud (Linode) ID-CGK (Jakarta), AU-MEL (Melbourne) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine in apac, au. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4d 2h it lasted.
Anything that failed between 2026-03-20 11:29 UTC and 2026-03-24 13:46 UTC may need a replay.Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai Cloud (Linode) 10
- investigating
Our team has identified the issue affecting connectivity in our Jakarta data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
provider
- investigating
Our team has identified the issue affecting connectivity in our Jakarta, ID data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
provider
- identified
We are continuing to implement a fix for the connectivity issue in our Jakarta, ID data center.
provider
- identified
We are still working to resolve the connectivity issue at our Jakarta, ID data center. While most services are recovering, some compute services in Jakarta may still be affected. Due to backend dependencies, there may also be impacts to nearby data centers Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel). Linode Kubernetes Engine (LKE) in these regions could experience disruptions because of a dependency with Jakarta, ID (id-cgk). We appreciate your patience and will provide further updates as we make progress.
provider
- identified
We are continuing to address the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services have recovered, but some compute services in Jakarta remain affected. Due to backend dependencies, customers in the Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) data centers may also experience disruptions, particularly with Linode Kubernetes Engine (LKE) deployments. Our teams are actively working to resolve these issues and restore full service. We appreciate your patience and will share further updates as progress is made.
provider
- identified
Our teams are continuing to mitigate the connectivity issue in Jakarta, ID and are working to restore full service. We appreciate your patience as we resolve the remaining disruptions.
provider
- identified
We are making steady progress toward full recovery of the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services in Jakarta are now operational. However, some Linodes and Linode Kubernetes Engine (LKE) clusters may still be affected, especially if nodes are provisioned or attempt to provision on impacted Linodes. The dependency issues that previously affected Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) have been resolved. We continue to work on restoring all services and appreciate your patience as we address the remaining issues. Further updates will be provided as progress continues.
provider
- identified
We are continuing to work on resolving the connectivity issue in our Jakarta, ID (id-cgk) data center. Thank you for your patience as we restore full service.
provider
- monitoring
At this time we have been able to correct the issues affecting connectivity in our Jakarta, ID data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
provider
- resolved
We haven’t observed any additional connectivity issues in our Jakarta, ID (id-cgk) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-824280322d
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-03-24 13:46 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
4d 2h, from 2026-03-20 11:29 UTC to 2026-03-24 13:46 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named ID-CGK (Jakarta), AU-MEL (Melbourne) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine in apac, au.
What caused it?
Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.