Linode incident

Connectivity Issue - Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2)

Minor Resolved View vendor source →
Started
Feb 27, 2026, 01:38 PM UTC
Resolved
Feb 27, 2026, 07:45 PM UTC
Duration
6h 7m
Detected by Pingoru
Feb 27, 2026, 01:38 PM UTC

Affected components

IN-MAA (Chennai)IN-BOM-2 (Mumbai 2)

Update timeline

  1. investigating Feb 27, 2026, 01:38 PM UTC

    Our team is investigating an issue affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers 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.

  2. monitoring Feb 27, 2026, 02:35 PM UTC

    At this time we have been able to correct the issues affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

  3. monitoring Feb 27, 2026, 03:48 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 27, 2026, 07:45 PM UTC

    We haven’t observed any additional connectivity issues in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

  5. postmortem Mar 07, 2026, 05:18 AM UTC

    Between February 27, 2026, 11:50 UTC and February 28, 2026, 17:40 UTC, Akamai observed degraded performance, intermittent connectivity issues, and packet loss affecting Edge Delivery and Cloud services for customers in India. The issue impacted multiple Edge locations and connectivity to Mumbai and Chennai data centers. The most significant impact occurred around 12:20 UTC on February 27, with a second window of disruption in the Mumbai region between 19:45 UTC and 21:00 UTC. A recurrence was identified on February 28, 2026, at 09:17 UTC. The recurrence was partially mitigated by 09:46 UTC and fully resolved by 11:08 UTC the same day. The root cause was a chain of unexpected subsea cable outages that occurred during repair work by the third-party network provider, resulting in intermittent disruptions to internet traffic between India and Europe. During the event, traffic was rerouted through unstable alternate paths by the third party provider, resulting in packet loss and congestion. Additionally, isolation of a key network point prevented effective traffic management, leading to service interruptions. Akamai took several actions to mitigate the impact, including suspending the traffic to the affected Edge locations, temporarily removing traffic from the affected ISP provider link, and closely monitoring the platform for stability. Once the third-party provider restored normal routing, Akamai removed temporary mitigations and confirmed service stability. The incident was fully mitigated by the third party provider at 15:34 UTC on March 3, 2026, after no further recurrences were observed. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Looking to track Linode downtime and outages?

Pingoru polls Linode's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Linode reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Linode alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Linode for free

5 free monitors · No credit card required