Linode Status

Current Status
Connectivity Issue - Chennai and Mumbai
Incident Report for Linode
Postmortem

At approximately 20:00 UTC on April 23rd, 2024, users accessing content through our network in India experienced disruptions due to actions taken by our upstream provider, Airtel. Outbound HTTP requests were redirected to Airtel's base page following a legal mandate, resulting in an inability to access any content. This issue primarily affected Cloudlets services and specific regions within India, impacting a portion of our user base.

In response to the incident, our network team applied mitigative measures, including deny-all actions for Airtel within our infrastructure. This action allowed us to restore normal operations and alleviate the impact on outbound HTTP requests, enabling users to regain access to desired content.

The issue was considered fully mitigated at 18:32 UTC on April 24th, 2024, following a period of close monitoring.

Moving forward, we are actively engaging with our upstream provider and internal teams to conduct a thorough investigation into the root cause of the issue. Additionally, we are reviewing our internal protocols and exploring further actions to enhance resilience against similar incidents in the future. 

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.

Posted May 02, 2024 - 22:01 UTC

Resolved
We haven’t observed any additional connectivity issues in our Chennai and Mumbai data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Apr 24, 2024 - 18:10 UTC
Monitoring
At this time we have been able to correct the issues affecting connectivity in our Chennai 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.
Posted Apr 24, 2024 - 06:20 UTC
Update
We are continuing to work with the third-party service provider to investigate this issue.
Posted Apr 24, 2024 - 01:27 UTC
Update
We are continuing to investigate this issue.
Posted Apr 23, 2024 - 23:42 UTC
Update
We are continuing to work with the third-party service provider to investigate this issue.
Posted Apr 23, 2024 - 23:35 UTC
Investigating
Our team has identified a third party issue affecting connectivity in our Chennai data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Posted Apr 23, 2024 - 22:41 UTC
This incident affected: Object Storage (IN-MAA (Chennai) Object Storage), Regions (AP-West (Mumbai), IN-MAA (Chennai)), Block Storage (AP-West (Mumbai) Block Storage, IN-MAA (Chennai) Block Storage), NodeBalancers (AP-West (Mumbai) NodeBalancers, IN-MAA (Chennai) NodeBalancers), Backups (AP-West (Mumbai) Backups, IN-MAA (Chennai) Backups), and Linode Kubernetes Engine (AP-West (Mumbai) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine).