Linode Status

Investigating: Our team is investigating an emerging service issue affecting Linode Manager and API in all Regions. We will share additional updates as we have more information.

Postmortem: Starting 08:15 UTC on September 24, 2025 customers began to experience a global degradation of service provisioning new Object Storage buckets, autoscaling of LKE resources, attaching Block Storage volumes to Linodes, and any other action which relies upon the Compute API for processing. Akamai was able to restore functionality at approximately 10:00 UTC on September 24, 2025.

The investigation revealed that the issue started as a result of unstable database performance, which began after a change release at 07:45 UTC on September 24, 2025. As the change propagated, database response times have increased and service became degraded.

To mitigate the issue, we rolled back the change at 08:41 UTC on September 24, 2025 and introduced database performance improvement actions so that our primary database can recover quicker. 

At this time our systems are operating as expected. A reoccurrence of this issue is unlikely, however, Akamai will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the inconvenience that this incident may have caused.

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 issues with the Cloud Manager, API or CLI, 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.

Monitoring: At this time we have been able to correct the issue affecting the Cloud Manager, API and CLI. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

Identified: Our team has identified the issue affecting the Cloud Manager, API and CLI. 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 a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.

Postmortem: Starting on September 5, 2025, at approximately 22:47 UTC, customers could have experienced timeouts and connectivity failures for traffic coming into and out of India, impacting our Chennai and Mumbai regions. The investigation revealed that the issue was due to an undersea cable cut and subsequent transit issues with multiple ISPs in India.

Traffic that was confined to India would not have been impacted. Other traffic that would not traverse the cut undersea cable coming into India would also not be affected.

At Akamai, we recognize that incidents involving undersea cables are largely beyond our control, and they can create additional pressures on international connections. When traffic is rerouted due to a cable issue, it often results in congestion on the remaining links, which can impact overall performance.

We took immediate action during this incident to minimize the effects on our customers. We implemented traffic redirection strategies to enhance performance wherever possible and closely monitored traffic conditions. We worked and collaborated with the affected ISPs to obtain real-time updates on the repair efforts.

As we work towards resolving this situation, our monitoring indicates that the most significant challenges were mainly between September 5 and 14, 2025. Customers might still experience increased latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks.

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 IN-MAA, AP-West, IN-BOM-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Connectivity to our India Compute regions (IN-MAA, AP-West, IN-BOM-2) has improved. Since September 14, 2025, we have not observed the recurring packet loss that previously affected traffic to and from EU & US locations during India peak business hours. Our network providers reported that backbone capacity in Asia has been stabilized and operations are largely restored. At this time, customers may still notice slightly higher latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks. We will continue to monitor the services.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. Between approximately 17:02 UTC and 18:20 UTC on September 12, 2025, we experienced an increase in intermittent connection failures and latency in all the services deployed in IN-MAA. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Identified: Linodes in our IN-MAA, AP-West, and IN-BOM data centers are experiencing increased network congestion and latency due to multiple faults in the undersea cables that are part of the optimal routes out of the data centers. There is currently no estimated time-to-resolution available from the undersea cable operators. We continue to work on mitigating customer impact with our third-party network providers and will share additional updates as soon as they become available.

Identified: We are continuing experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data center. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: Our team is investigating an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our AP-West and IN-BOM-2 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 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: Our team investigated an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. The issue started at 11:00 UTC on September 27, 2025, and was mitigated at 12:19 UTC on September 27, 2025. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in this data center. At this time, we have been able to correct the issues affecting connectivity. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Postmortem: Starting on September 5, 2025, at approximately 22:47 UTC, customers could have experienced timeouts and connectivity failures for traffic coming into and out of India, impacting our Chennai and Mumbai regions. The investigation revealed that the issue was due to an undersea cable cut and subsequent transit issues with multiple ISPs in India.

Traffic that was confined to India would not have been impacted. Other traffic that would not traverse the cut undersea cable coming into India would also not be affected.

At Akamai, we recognize that incidents involving undersea cables are largely beyond our control, and they can create additional pressures on international connections. When traffic is rerouted due to a cable issue, it often results in congestion on the remaining links, which can impact overall performance.

We took immediate action during this incident to minimize the effects on our customers. We implemented traffic redirection strategies to enhance performance wherever possible and closely monitored traffic conditions. We worked and collaborated with the affected ISPs to obtain real-time updates on the repair efforts.

As we work towards resolving this situation, our monitoring indicates that the most significant challenges were mainly between September 5 and 14, 2025. Customers might still experience increased latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks.

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 IN-MAA, AP-West, IN-BOM-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Connectivity to our India Compute regions (IN-MAA, AP-West, IN-BOM-2) has improved. Since September 14, 2025, we have not observed the recurring packet loss that previously affected traffic to and from EU & US locations during India peak business hours. Our network providers reported that backbone capacity in Asia has been stabilized and operations are largely restored. At this time, customers may still notice slightly higher latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks. We will continue to monitor the services.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. Between approximately 17:02 UTC and 18:20 UTC on September 12, 2025, we experienced an increase in intermittent connection failures and latency in all the services deployed in IN-MAA. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Identified: Linodes in our IN-MAA, AP-West, and IN-BOM data centers are experiencing increased network congestion and latency due to multiple faults in the undersea cables that are part of the optimal routes out of the data centers. There is currently no estimated time-to-resolution available from the undersea cable operators. We continue to work on mitigating customer impact with our third-party network providers and will share additional updates as soon as they become available.

Identified: We are continuing experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data center. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: Our team is investigating an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our AP-West and IN-BOM-2 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 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: Our team investigated an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. The issue started at 11:00 UTC on September 27, 2025, and was mitigated at 12:19 UTC on September 27, 2025. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in this data center. At this time, we have been able to correct the issues affecting connectivity. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Postmortem: Starting on September 5, 2025, at approximately 22:47 UTC, customers could have experienced timeouts and connectivity failures for traffic coming into and out of India, impacting our Chennai and Mumbai regions. The investigation revealed that the issue was due to an undersea cable cut and subsequent transit issues with multiple ISPs in India.

Traffic that was confined to India would not have been impacted. Other traffic that would not traverse the cut undersea cable coming into India would also not be affected.

At Akamai, we recognize that incidents involving undersea cables are largely beyond our control, and they can create additional pressures on international connections. When traffic is rerouted due to a cable issue, it often results in congestion on the remaining links, which can impact overall performance.

We took immediate action during this incident to minimize the effects on our customers. We implemented traffic redirection strategies to enhance performance wherever possible and closely monitored traffic conditions. We worked and collaborated with the affected ISPs to obtain real-time updates on the repair efforts.

As we work towards resolving this situation, our monitoring indicates that the most significant challenges were mainly between September 5 and 14, 2025. Customers might still experience increased latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks.

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 IN-MAA, AP-West, IN-BOM-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Connectivity to our India Compute regions (IN-MAA, AP-West, IN-BOM-2) has improved. Since September 14, 2025, we have not observed the recurring packet loss that previously affected traffic to and from EU & US locations during India peak business hours. Our network providers reported that backbone capacity in Asia has been stabilized and operations are largely restored. At this time, customers may still notice slightly higher latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks. We will continue to monitor the services.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. Between approximately 17:02 UTC and 18:20 UTC on September 12, 2025, we experienced an increase in intermittent connection failures and latency in all the services deployed in IN-MAA. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Identified: Linodes in our IN-MAA, AP-West, and IN-BOM data centers are experiencing increased network congestion and latency due to multiple faults in the undersea cables that are part of the optimal routes out of the data centers. There is currently no estimated time-to-resolution available from the undersea cable operators. We continue to work on mitigating customer impact with our third-party network providers and will share additional updates as soon as they become available.

Identified: We are continuing experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data center. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: Our team is investigating an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our AP-West and IN-BOM-2 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 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.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Identified: We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.

Monitoring: Our team investigated an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. The issue started at 11:00 UTC on September 27, 2025, and was mitigated at 12:19 UTC on September 27, 2025. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in this data center. At this time, we have been able to correct the issues affecting connectivity. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.

Resolved: We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.

Identified: Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. 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 issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.

Identified: Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. 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 issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.

Identified: Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. 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 issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.

Identified: Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. 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 issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.

Identified: Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. 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 issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.