Linode Status

Resolved: We haven't observed any additional issues, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Investigating: Our team is actively investigating the issue affecting Linode Manager and API, which is causing duplicate notification emails for some customers. We appreciate your patience as we work to resolve this. We will provide further updates as soon as we have more information.

Investigating: We are continuing to investigate the issue. We will share additional updates as we have more information and once progress is made.

Investigating: We are aware some customers are receiving duplicate notification emails in fixed intervals. Additional updates will be shared once we have more information.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.

Investigating: We are continuing to investigate this issue.

Investigating: This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.

Resolved: Our team has identified that the issue affecting the Cloud Manager and API is related to a previously communicated incident from March 4, 2026 (https://status.linode.com/incidents/yzlp8ykymmhm). Today's issue was caused by the backlog of notifications that accumulated due to the previous incident, and it has cleared now. We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Investigating: We are continuing to investigate this issue. As a workaround, customers can login to https://cloud.linode.com/ and manually check the notifications until the issue is mitigated. Subsequent updates will be posted as progress is made.

Investigating: We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates will be posted as progress is made.

Investigating: Our team is investigating an emerging issue where some customers are receiving delayed event notification or notification emails for activities performed on Cloud Manager. We will share additional updates as we have more information.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IAD (Washington, DC) 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 the issue affecting connectivity in our IAD (Washington, DC) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating an emerging service issue affecting compute hosts in IAD (Washington, DC). We will share additional updates as we have more information.

Postmortem: 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.

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.

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.

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.

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.

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.

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.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.

Investigating: We are continuing to investigate this issue.

Investigating: This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.

Investigating: We are continuing to investigate this issue.

Investigating: This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.

Investigating: We are continuing to investigate this issue.

Investigating: This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.

Investigating: We are continuing to investigate this issue.

Investigating: This issue is impacting Object Storage access globally. During this time customers may encounter issues with managing buckets, access keys, or Object Storage policies. Our team is continuing to investigate.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are still working to implement the fix for the Object Storage service issue. We will share another update as soon as progress is made.

Identified: Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is continuing to investigate the Object Storage API issue, which affects all Object Storage regions. This issue is limited to interacting with the Object Storage service, such as managing buckets, access keys, or Object Storage policies. The underlying Object Storage service itself remains operational. We appreciate your patience and will provide further updates as soon as possible.

Investigating: We are continuing to investigate this issue. Thank you for your patience as we work toward a resolution.

Investigating: We are actively investigating an issue affecting the Object Storage service. Users may experience connection timeouts and errors when accessing this service. We will provide updates as we learn more and work toward a resolution.