Linode incident: Connectivity Issue - AP-West (Mumbai) and IN-MAA (Chennai)

Affected components

• AP-West (Mumbai)
• IN-MAA (Chennai)

1. postmortemMay 14, 2026, 15:10 UTC

   On May 12, 2026, at approximately 14:50 UTC, Akamai began experiencing congestion and packet loss affecting traffic between India and Europe over Internet Service Provider network paths servicing our Mumbai and Chennai data centers. Customers may have seen intermittent connection timeouts and errors in the affected regions. The issue was due to congestion on transit paths between India and Europe. Akamai worked with the involved Internet Service Providers and their upstream providers to identify the cause. To mitigate the impact, Akamai redirected traffic away from the affected paths, stabilizing service while the investigation continued. Service was restored at the Mumbai data center at 19:23 UTC on May 12, 2026, and at the Chennai data center at 00:25 UTC on May 13, 2026. Akamai will continue working with the involved Internet Service Providers to address the underlying congestion and help prevent recurrence. This summary reflects our current understanding of the incident based o

2. resolvedMay 13, 2026, 01:02 UTC

   This incident has been resolved. While we continue to monitor the upstream provider's progress on their underlying connectivity issue, our services are now stable on alternative paths.

3. identifiedMay 12, 2026, 22:47 UTC

   We are continuing to work with our service provider on a fix for this issue.

4. identifiedMay 12, 2026, 19:52 UTC

   Our third-party service provider has identified the issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers, and a fix is being implemented. We will provide an update as soon as the solution is in place.

5. investigatingMay 12, 2026, 17:54 UTC

   We are continuing to investigate the issue with our service provider. We will share additional updates as we have more information.

6. investigatingMay 12, 2026, 17:12 UTC

   Our team is investigating an issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers. During this time, users may experience intermittent connection timeouts and errors for all services deployed in these data centers. We will share additional updates as we have more information.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Render: Logs unavailable for some services in all regionsMajor · May 12, 2026, 22:29 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Akamai: Bot Manager Premier IssuesMinor · May 11, 2026, 16:03 UTC
• ReadMe: Degraded performance across Admin HubsMinor · May 12, 2026, 14:15 UTC
• Akamai: Edge Delivery Issues between India and EuropeMinor · May 12, 2026, 18:39 UTC

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history