Connectivity Issue - Chennai
Incident
Report for Linode
Postmortem
On April 11, 2024 at approximately 5:30 UTC, connectivity issues were detected in the Chennai data center. At 5:48 UTC, our admins were alerted to these connectivity issues and began investigating. At 6:30 UTC they began to suspend traffic in order to temporarily mitigate the incident. At around 6:46 UTC, our admins determined that multiple fiber cuts were impacting an ISP in the region and causing the connectivity issues.
At approximately 10:30 UTC, the ISP confirmed resolution of the fiber cut issue on their end and our admins began to unsuspend traffic and monitor for any packet loss. After a period of monitoring, connectivity was confirmed to be stable once again and the incident was considered resolved at 18:58 UTC.
Resolved
We haven’t observed any additional connectivity issues in our Chennai data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Update
We are continuing to monitor for any further issues. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
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.
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.
This incident affected: Object Storage (IN-MAA (Chennai) Object Storage), Backups (IN-MAA (Chennai) Backups), Block Storage (IN-MAA (Chennai) Block Storage), NodeBalancers (IN-MAA (Chennai) NodeBalancers), Linode Kubernetes Engine (IN-MAA (Chennai) Linode Kubernetes Engine), and Regions (IN-MAA (Chennai)).