- Level
- confirmed
- Worst impact
- Degraded
- Components
- AP-West (Mumbai)
- Regions
- apac
What to do
Check whether you use Akamai Cloud (Linode) AP-West (Mumbai) in apac. 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 3d 20h it lasted.
Anything that failed between 2026-02-27 21:00 UTC and 2026-03-03 17:30 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) 6
- investigating
Our team is investigating an issue affecting connectivity in our Mumbai, IN (in-mum) data center During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.
provider
- monitoring
At this time we have been able to correct the issues affecting connectivity in our Mumbai, IN (in-mum) 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
- identified
We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region. Our team is investigating and we will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
provider
- investigating
At this time we have been able to apply mitigation actions that improve the experience for customers connecting to our Mumbai, IN (in-mum) data center. In the meantime, we are actively investigating the issue with our third-party and will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
provider
- monitoring
We have taken mitigation steps and escalated to our third-party service provider in our Mumbai, IN (in-mum) data center, who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.
provider
- resolved
We haven’t observed any additional connectivity issues in our Mumbai, IN (in-mum) 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-091fe6c965
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-03-03 17:30 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
3d 20h, from 2026-02-27 21:00 UTC to 2026-03-03 17:30 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named AP-West (Mumbai) in apac.
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.