Linode Outage History

Started Feb 17, 2026, 01:59 PM UTC· resolved Feb 18, 2026, 12:26 PM UTC

1. investigating Feb 17, 2026, 01:59 PM UTC

   Our team is investigating an emerging service issue affecting Network Connectivity in EU-West (London). We will share additional updates as we have more information.

2. identified Feb 17, 2026, 04:13 PM UTC

   We've identified the cause of network performance degradation in EU-West (London) and are working to mitigate the impact.

3. monitoring Feb 17, 2026, 05:45 PM UTC

   At this time we have been able to correct the issues affecting connectivity in our EU-West (London) 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.

4. identified Feb 17, 2026, 06:43 PM UTC

   We have found continued issues of network performance degradation in EU-West (London) effecting traffic and are working to mitigate the impact

5. monitoring Feb 17, 2026, 10:58 PM UTC

   We have been able to mitigate an additional issue that was affecting a subset of user's connectivity in our EU-West (London) 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.

6. resolved Feb 18, 2026, 12:26 PM UTC

   We haven’t observed any additional connectivity issues in our EU-West (London) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Started Feb 12, 2026, 01:26 PM UTC· resolved Feb 12, 2026, 03:19 PM UTC

1. monitoring Feb 12, 2026, 01:26 PM UTC

   Our team is aware of an issue that affected the Block Storage service in Stockholm between 07:40 and 10:52 AM UTC on February 12, 2026. During this time, users may have experience stuck operations on attached volumes. At this time we have been able to correct the issues affecting the Block 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.

2. resolved Feb 12, 2026, 03:19 PM UTC

   We haven’t observed any additional issues with the Block Storage service in SE-STO (Stockholm), and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

3. postmortem Feb 25, 2026, 11:39 AM UTC

   Between 07:40 and 10:52 UTC on February 12, 2026, some customers experienced issues accessing their Block Storage volumes in the Stockholm region. During this period, storage operations stalled, resulting in a temporary denial of service for affected users. Monitoring detected a complete drop in storage throughput, and impacted customers were unable to access data on their volumes during the impact window. The incident was traced to a gap in the execution sequence during a recent storage system upgrade, which resulted in the storage environment entering a degraded state. The scenario was documented, however it was not clearly incorporated into the upgrade workflow, as it had not been encountered in previous upgrades. To mitigate the impact, Akamai initiated recovery actions and restored normal working service. In response, the upgrade process has been updated to include clearer guidance for handling similar situations. 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

Read the full incident report →

Started Feb 12, 2026, 02:29 AM UTC· resolved Feb 12, 2026, 04:23 AM UTC

1. monitoring Feb 12, 2026, 02:29 AM UTC

   Starting around 11:04 UTC on February 10, 2026, Longview graph dashboard became unavailable. The investigation revealed that an internal certificate expiry caused the issue. The impact was limited to reading the existing reporting data, and there was no permanent reporting data loss due to this issue. The affected certificate was rotated to mitigate the impact. The impact was mitigated at 23:44 UTC on February 10, 2026. We will continue to monitor to ensure that the impact has been fully mitigated.

2. resolved Feb 12, 2026, 04:23 AM UTC

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

3. postmortem Feb 16, 2026, 01:52 AM UTC

   Starting around 11:04 UTC on February 10, 2026, some customers were unable to access the Longview graph dashboard. Longview is a system data graphing service that tracks metrics for CPU, memory, and network bandwidth on both an aggregate and per-process basis. It also provides real-time graphs that can help expose performance problems \(more details about Longview are available [here](https://techdocs.akamai.com/cloud-computing/docs/longview)\). The investigation revealed that the issue was caused by an internal certificate expiry for the [longview.linode.com](http://longview.linode.com) hostname. The impact was limited to reading the existing reporting data only, while the write operations remained unaffected, and there was no permanent reporting data loss due to this issue. Akamai's internal automated tool rotated the expiring certificate before the certificate expired; however, the internal certificate tool which was supposed to auto-reload the system, did not reload the Longview servers after the previous certificate was rotated. The issue started when the previous certificate expired. To mitigate the impact, we manually reloaded the Longview servers for the new certificate to take effect. The impact was mitigated at 23:44 UTC on February 10, 2026, following this action. We will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. 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.

Read the full incident report →

Started Feb 04, 2026, 02:41 PM UTC· resolved Feb 04, 2026, 02:41 PM UTC

1. resolved Feb 04, 2026, 03:35 PM UTC

   Starting at 14:43 UTC on February 4, 2026, users in our London (gb-lon) region may have encountered 500 errors when accessing object storage. We identified the issue quickly and resolved it by 15:19 UTC the same day. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please open a Support ticket for assistance.

2. postmortem Feb 09, 2026, 07:30 PM UTC

   On February 4, 2026, starting at 14:43 UTC, users accessing [gb-lon-1.linodeobjects.com](http://gb-lon-1.linodeobjects.com) experienced increased error rates due to an issue with one of the storage backends supporting the London Object Storage service. During this period, success rates dropped to between 93% and 95%. Our team identified that one of the six storage backends was experiencing problems, which affected service availability. The affected components recovered on their own, and service success rates returned to normal by 15:19 UTC. We are continuing to investigate the underlying cause of the backend issue and will implement additional safeguards to help prevent similar incidents. Thank you for your patience as we work to enhance service reliability. This summary reflects our current understanding of the incident. Our investigation is ongoing, and details may be updated as more information becomes available.

Read the full incident report →

Started Jan 23, 2026, 07:16 PM UTC· resolved Jan 27, 2026, 06:55 PM UTC

1. monitoring Jan 23, 2026, 07:16 PM UTC

   Akamai is aware of an upcoming winter storm set to affect the continental United States during the upcoming days (https://www.wpc.ncep.noaa.gov/wwd/wssi/wssi.php). Akamai is working with our vendors to ensure proper preparedness to withstand the storm and take actions in case they are needed. We are actively monitoring the situation to ensure that services remain stable. If you are experiencing issues and are 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]. Our general best practice guidelines for all customers is to maintain redundancy of critical systems across multiple regions at all times. We also recommend that all customers maintain a robust backup strategy for their services at all times. Compute instances can be cloned or migrated to other datacenters through our self-service Cloud Manager or API tools. Note that migrating services between datacenters will result in changes to Backups and IPv4 and v6 endpoints: Migration Resources https://techdocs.akamai.com/cloud-computing/docs/migrate-to-a-new-data-center https://techdocs.akamai.com/linode-api/reference/post-migrate-linode-instance Cloning Resources https://techdocs.akamai.com/cloud-computing/docs/clone-a-compute-instance https://techdocs.akamai.com/linode-api/reference/post-clone-linode-instance

2. resolved Jan 27, 2026, 06:55 PM UTC

   After monitoring our systems, we haven’t observed any issues with our services related to the winter storm. We will now consider this notification resolved.

Read the full incident report →

Started Jan 20, 2026, 08:13 PM UTC· resolved Jan 21, 2026, 04:17 AM UTC

1. investigating Jan 20, 2026, 08:13 PM UTC

   Our team is investigating an issue affecting connectivity in our London (EU-West) 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.

2. monitoring Jan 21, 2026, 01:02 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jan 21, 2026, 04:17 AM UTC

   This incident is resolved.

Read the full incident report →

Started Jan 09, 2026, 03:05 AM UTC· resolved Jan 09, 2026, 03:05 AM UTC

1. resolved Jan 09, 2026, 05:09 PM UTC

   On January 9, 2026, between 03:05 and 04:28 UTC, we observed a connectivity issue affecting services in the Jakarta, Indonesia (ID-CGK) region. During this time, some users may have experienced packet loss or reduced network performance. We haven’t observed any additional connectivity issues in our ID-CGK region since 04:28 UTC on January 9, 2026, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

2. postmortem Jan 15, 2026, 07:55 PM UTC

   On January 9, 2026, at 03:05 UTC, we detected significant packet loss affecting two Compute sites in the Jakarta, Indonesia \(ID-CGK\) region. This incident resulted in intermittent connectivity issues for customers, including slow or failed access to services, increased latency, timeouts, and disruptions in network-dependent applications. Our investigation identified the root cause as a BGP route leak originating from a peer in Indonesia. This route leak disrupted normal routing paths, leading to degraded network performance for users accessing services in the affected region. We worked quickly to isolate and address the routing issue, and by 04:28 UTC, routing had returned to normal. At this time we have not observed any recurrence of the issue. To help prevent similar incidents, we have fine-tuned our network monitoring and alerting systems to detect connectivity issues more quickly. This improvement enables us to respond faster to potential disruptions and maintain reliable service for our customers. We apologize for any inconvenience this incident caused and remain committed to providing reliable service. 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.

Read the full incident report →

Started Dec 22, 2025, 08:27 PM UTC· resolved Dec 24, 2025, 02:49 PM UTC

1. investigating Dec 22, 2025, 08:27 PM UTC

   Our team is investigating an emerging service issue affecting Object Storage in Chicago. Specifically, we are investigating an issue that is preventing Lifecycle policies from being carried out as expected on the E1 endpoint (us-ord-1.linodeobjects.com). We will share additional updates as we have more information.

2. investigating Dec 23, 2025, 11:21 AM UTC

   We are continuing to investigate this issue. We will share additional updates as we have more information.

3. identified Dec 23, 2025, 03:52 PM UTC

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

4. monitoring Dec 23, 2025, 10:39 PM UTC

   At this time we have been able to correct the issue affecting the Object Storage service in Chicago. 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].

5. resolved Dec 24, 2025, 02:49 PM UTC

   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.

6. postmortem Jan 06, 2026, 07:10 AM UTC

   Around 04:14 UTC on December 19, 2025, Akamai identified an issue with one Object Storage system in Chicago that caused Lifecycle \(LC\) processing to fail. As a result, data was not deleted as expected, leading to data buildup and over-quota conditions for some customers. The investigation determined that a Ceph version mismatch was the root cause of the LC processing failures. The issue was resolved by performing the required upgrades, and the impact was mitigated by approximately 12:25 UTC on December 24, 2025. To prevent recurrence, Akamai will review the actions taken as well as the relevant procedures and implement the necessary changes. 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.

Read the full incident report →

Started Dec 22, 2025, 08:04 PM UTC· resolved Dec 23, 2025, 04:24 AM UTC

1. investigating Dec 22, 2025, 08:04 PM UTC

   We are currently investigating an issue impacting Block Storage volume attachment/detachment and reachability in the IAD data center.

2. monitoring Dec 22, 2025, 08:49 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Dec 23, 2025, 04:24 AM UTC

   We have resolved the issue that prompted this emerging status event. Customers may have experienced a brief period of impact, during which general performance and usability to the Block Storage service in IAD were affected. At this time, we are confident that the service is fully operational. If you encounter any further issues, please contact Compute Support for assistance. We apologize for this inconvenience.

Read the full incident report →

Started Dec 16, 2025, 01:44 AM UTC· resolved Dec 16, 2025, 05:17 AM UTC

1. investigating Dec 16, 2025, 01:44 AM UTC

   Our team is investigating an issue in the US-Southeast (Atlanta) data center. During this time, users may experience interruption of service or will be unable to access their Linodes. The impact is limited to some hosts in this data center. We will share additional updates as we have more information.

2. investigating Dec 16, 2025, 02:42 AM UTC

   We are continuing to investigate this issue. We will share additional updates as we have more information.

3. investigating Dec 16, 2025, 03:08 AM UTC

   Our team has identified the issue in the US-Southeast (Atlanta) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

4. monitoring Dec 16, 2025, 04:31 AM UTC

   At this time, we have been able to correct the issues affecting connectivity in our US-Southeast (Atlanta) 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.

5. resolved Dec 16, 2025, 05:17 AM UTC

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

6. postmortem Dec 16, 2025, 06:25 AM UTC

   Starting around 23:15 UTC on December 15, 2025, Akamai received several internal alerts indicating issues with some hosts in the US-Southeast \(Atlanta\) data center \(ATL1 DC\). The investigation revealed that the issue was caused by a power supply failure in one of the racks in this data center. Customers with Linodes on these hosts would have experienced an interruption in the service. As part of the mitigation effort, Akamai manually turned down these hosts at around 02:00 UTC on December 16, 2025, and started the drive transplant activity, which was to migrate the customers to another rack. Drive transplant was believed to be the fastest mitigation action, without knowing the root cause of the outage. Further investigation indicated that the loss of power supply was due to a planned maintenance activity at the data center. The planned maintenance was communicated to Akamai, but the internal teams missed migrating the customers to another rack \(before the maintenance\) due to an internal communication gap. The power supply was restored around 03:10 UTC on December 16, 2025. However, the drive transplant action was in progress at that time, and customer impact continued until the completion of the drive transplant activity at around 04:20 UTC on December 16, 2025. We will continue to investigate the root cause of the communication gap and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. 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.

Read the full incident report →

Started Dec 09, 2025, 04:25 PM UTC· resolved Dec 10, 2025, 02:41 AM UTC

1. investigating Dec 09, 2025, 04:25 PM UTC

   Our team is investigating an issue affecting connectivity in our US-IAD (Washington) 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.

2. investigating Dec 09, 2025, 05:14 PM UTC

   We continue to investigate the issue and shall provide an update as we progress.

3. investigating Dec 09, 2025, 07:09 PM UTC

   We are continuing to investigate connectivity issues in the US-IAD (Washington) data center. Users may experience intermittent timeouts and errors for services hosted there. We will provide updates as more information becomes available.

4. investigating Dec 09, 2025, 10:43 PM UTC

   We are continuing to investigate this issue.

5. resolved Dec 10, 2025, 02:41 AM UTC

   We haven't observed any additional connectivity issues in our US-IAD (Washington) data center 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.

Read the full incident report →

Started Dec 08, 2025, 04:38 PM UTC· resolved Dec 09, 2025, 04:59 PM UTC

1. investigating Dec 08, 2025, 04:38 PM UTC

   Our team is investigating an emerging service issue affecting completing jobs issued to compute hosts in multiple regions. We will share additional updates as we have more information.

2. identified Dec 08, 2025, 05:13 PM UTC

   Our team has identified the issue affecting jobs being issued and completed on compute hosts. We are working quickly to implement a fix to these hosts, and we will provide an update as soon as the solution is in place. If you continue experiencing issues or need further assistance, please open a Support ticket from the Linode Manager.

3. monitoring Dec 08, 2025, 09:17 PM UTC

   At this time we have been able to correct the issue affecting jobs being issued and completed on Compute hosts. 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].

4. resolved Dec 09, 2025, 04:59 PM UTC

   We haven't observed any additional issues with jobs being issued and completed on Compute hosts, 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.

5. postmortem Dec 12, 2025, 03:38 PM UTC

   Beginning at ~14:40 UTC on December 8, 2025, a subset of Compute hosts began to experience errors resolving DNS names including a core Linode database endpoint. Most Compute hosts had an active database connection and were able to process new jobs without impact. At that time a separate deployment of a new internal service was in process which required restarting the service and the re-establishment of database connections. Due to this restart, these hosts disconnected from the database and were unable to reconnect due to the DNS resolution problem. This issue was due to a recent infrastructure code configuration update to switch these hosts to internal DNS resolvers over IPv6. The change was intended to be applied only to storage systems and unintentionally was applied to all hosts including Compute hosts.Once the offending configuration change was isolated, it was reverted. To resolve the issue, we worked through the impacted hosts, updating configurations in batches, so as to not introduce additional unnecessary impact, fully mitigating the issue at ~21:17 UTC on December 8, 2025. To prevent this issue from occurring in the future, we will decouple the currently-shared configurations whose update led to this impact. 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.

Read the full incident report →

Started Dec 05, 2025, 05:48 PM UTC· resolved Dec 05, 2025, 10:55 PM UTC

1. investigating Dec 05, 2025, 05:48 PM UTC

   Our team is investigating an emerging service issue affecting Object Storage in it-mil (Milan, Italy). We will share additional updates as we have more information.

2. resolved Dec 05, 2025, 10:55 PM UTC

   After further investigation it was determined that this issue is not causing any customer impact or service disruption, we apologize for the confusion.

Read the full incident report →

Started Dec 04, 2025, 05:43 PM UTC· resolved Dec 05, 2025, 12:40 AM UTC

1. investigating Dec 04, 2025, 05:43 PM UTC

   Our team is investigating a service issue affecting the Managed Databases service. During this time, users may experience issues when attempting to configure, update, provision, and view Managed Databases via the Cloud Manager or Linode API. Existing Managed Database cluster operations are not affected. We will share additional updates as we have more information.

2. investigating Dec 04, 2025, 06:50 PM UTC

   We are continuing to investigate this issue.

3. monitoring Dec 04, 2025, 07:12 PM UTC

   At this time we have been able to confirm the issue affecting the Cloud Manager and API was related to a vendor having issues on their side, these issues have been fixed on their end and our services are back on line as of 18:55 UTC. 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].

4. monitoring Dec 04, 2025, 08:14 PM UTC

   There was a recurrence from 19:28 UTC to 19:42 UTC because our third party experienced issues again while working on their end. We can confirm the issue is no longer happening at this moment. We are continuing to monitor for any further issues.

5. resolved Dec 05, 2025, 12:40 AM UTC

   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.

6. postmortem Dec 18, 2025, 06:15 PM UTC

   On December 4th at approximately 16:30 UTC we became aware of connectivity issues impacting Cloud Manager and Linode API, during this time, users may have experienced issues accessing the UI and/or when attempting to configure, update, provision, and view Managed Databases via the Cloud Manager or Linode API. Existing Managed Database cluster operations were not affected. The connectivity issue was caused by an outage with a third-party provider that supplies metrics used by our Managed Database services. The provider’s metrics API failed, which resulted in 500 errors across database-related API endpoints. The issue was resolved by the third-party provider, and services were restored at 18:55 UTC on December 4th. A brief recurrence occurred between 19:28 UTC and 19:42 UTC while a permanent fix was being applied. No further impact has been observed since. We will continue to work closely with our third party while they implement additional measures to avoid issues like this 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.

Read the full incident report →

Started Dec 03, 2025, 03:15 PM UTC· resolved Oct 08, 2026, 09:26 PM UTC

1. investigating Dec 03, 2025, 03:15 PM UTC

   Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.

2. identified Dec 03, 2025, 04:48 PM UTC

   Our team has identified the issue affecting booting up GPU and VPU plans. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

3. identified Dec 04, 2025, 08:51 PM UTC

   We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

4. identified Dec 17, 2025, 01:40 PM UTC

   We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

5. identified Jan 05, 2026, 05:16 PM UTC

   We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

6. identified Jan 05, 2026, 07:30 PM UTC

   We have successfully identified a solution to address the issue at hand. We are currently in the testing phase prior to initiating the rollout of the fix. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

7. identified Feb 03, 2026, 03:34 PM UTC

   We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

8. identified Feb 19, 2026, 04:41 PM UTC

   We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

9. identified Feb 26, 2026, 03:42 PM UTC

   We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

10. identified Mar 19, 2026, 08:13 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

11. identified Apr 06, 2026, 01:39 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

12. identified Apr 15, 2026, 03:12 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

13. identified May 13, 2026, 08:59 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

14. identified May 26, 2026, 09:17 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

15. identified Jul 03, 2026, 01:55 PM UTC

    We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

16. resolved Oct 08, 2026, 09:26 PM UTC

    We haven’t observed any additional issues with GPU plans, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Started Nov 24, 2025, 05:32 PM UTC· resolved Dec 02, 2025, 06:31 PM UTC

1. investigating Nov 24, 2025, 05:32 PM UTC

   Our team is investigating an issue affecting connectivity between our Australia (Melbourne) region and North America. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this region. We will share additional updates as we have more information.

2. monitoring Nov 24, 2025, 06:54 PM UTC

   At this time we have been able to correct the issues affecting connectivity in our Australia (Melbourne and Sydney) regions and North America (Los Angeles) region. 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. investigating Nov 25, 2025, 03:39 PM UTC

   Our investigation found that the issue is also impacting connectivity between New Zealand and other Non-Oceanic regions. Our team has identified the issue affecting connectivity to our Australia and New-Zealand DataCenter. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

4. monitoring Nov 25, 2025, 05:58 PM UTC

   At this time we have been able to correct the issues affecting connectivity between Australia/New Zealand and other non-Oceanic regions. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

5. resolved Dec 02, 2025, 06:31 PM UTC

   We haven’t observed any additional connectivity issues between our Australia/New Zealand region and non-Oceanic regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

6. postmortem Jan 27, 2026, 09:41 PM UTC

   Beginning approximately 11:00 UTC on November 19, 2025, Linode-to-Linode traffic between Singapore and Oceania \(Australia/New Zealand\) and intra-Oceania traffic experienced periods of service degradation and delays between ~11:00 UTC and 16:30 UTC due to unexpected onboarding of customer traffic beyond capacity, resulting in suboptimal out-of-country \(OOC\) routing. This issue was mitigated by a combination of route mapping optimizations applied to the customer’s traffic as well as a return of off-line capacity in the region. Spikes in OOC routing subsided on December 23, 2025. To prevent this issue from occurring in the future, we are reviewing our approval process for onboarding large traffic sets as well as how the platform responds to significant increases in traffic to ensure that impact to existing traffic is minimized. 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.

Read the full incident report →

Started Nov 22, 2025, 04:43 PM UTC· resolved Nov 25, 2025, 10:24 PM UTC

1. identified Nov 22, 2025, 04:43 PM UTC

   Our team has identified impact from an undersea cable maintenance affecting connectivity in and to our Singapore regions. This maintenance is scheduled to complete at 22:00 UTC on November 22, 2025. 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 Nov 22, 2025, 05:54 PM UTC

   At this time we have been able to identify that the issues impacting connectivity in our Singapore regions has been mitigated. We will be monitoring this to ensure that the undersea cable maintenance completes successfully and that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

3. identified Nov 24, 2025, 03:09 PM UTC

   We are reviewing a potential recurrence of this issue in our Singapore data center starting at approximately 12:00 UTC on November 24th, 2025. During this time, users may experience intermittent connection timeouts and errors for all services in this location. We will provide an update once we have more information to share.

4. monitoring Nov 24, 2025, 04:22 PM UTC

   We have confirmed that the issue identified today is unrelated to this incident and will be triaging and communicating it separately. We apologize for the confusion.

5. resolved Nov 25, 2025, 10:24 PM UTC

   We haven’t observed any additional connectivity issues in our Singapore regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Started Nov 22, 2025, 11:37 AM UTC· resolved Dec 18, 2025, 10:32 PM UTC

1. investigating Nov 22, 2025, 11:37 AM UTC

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

2. investigating Nov 22, 2025, 12:25 PM UTC

   We are continuing to investigate this issue. We will share additional updates as we have more information.

3. investigating Nov 22, 2025, 02:02 PM UTC

   Our team is continuing to investigate the root cause of a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. We applied mitigation steps and systems began recovering at approximately 13:35 UTC on Saturday November 22, 2025. We will share additional updates as we have more information.

4. investigating Nov 22, 2025, 02:07 PM UTC

   We are continuing to investigate this issue.

5. monitoring Nov 22, 2025, 03:14 PM UTC

   At this time we have been able to correct the issue affecting the Cloud Manager and API. 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].

6. monitoring Dec 03, 2025, 10:56 PM UTC

   We are continuing to monitor 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].

7. resolved Dec 18, 2025, 10:32 PM UTC

   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.

8. postmortem Dec 23, 2025, 01:45 AM UTC

   On November 22, 2025, between approximately 10:40 UTC and 13:35 UTC, Akamai experienced query congestion due to lock contention on a database backing Compute infrastructure. During this time, customers would have experienced issues creating, autoscaling, or otherwise managing Linodes. Customer support was also impacted by an inability to update customer cases during this timeframe. To mitigate this issue, Akamai identified multiple long-running queries at the core of the contention and manually stopped them to allow the standard flow of read/write operations to resume, restoring service. To prevent this issue from occurring again, Akamai will implement additional monitoring and automated remediation processes based on findings from this incident. 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.

Read the full incident report →

Started Nov 21, 2025, 01:26 PM UTC· resolved Nov 21, 2025, 05:51 PM UTC

1. investigating Nov 21, 2025, 01:26 PM UTC

   Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE) impacting networking to some cluster control planes. We will share additional updates as we have more information.

2. investigating Nov 21, 2025, 02:30 PM UTC

   We are continuing to investigate this issue.

3. investigating Nov 21, 2025, 02:59 PM UTC

   We have also confirmed this issue is impacting the NodeBalancer service in Atlanta, Frankfurt, Mumbai, Singapore, Newark, and Toronto data centers. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.

4. identified Nov 21, 2025, 03:27 PM UTC

   Our team has identified the issue affecting the LKE and NodeBalancers services. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

5. monitoring Nov 21, 2025, 03:49 PM UTC

   At this time, we have been able to correct the issues affecting the LKE and NodeBalancers services. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

6. resolved Nov 21, 2025, 05:51 PM UTC

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

7. postmortem Nov 24, 2025, 08:28 PM UTC

   On November 21, 2025, at approximately 09:52 UTC, customers started reporting that their LKE API endpoints were dropping connections, preventing them from connecting to the LKE API server. Additionally, customers experienced connection timeouts and errors in NodeBalancers. This issue was observed in the following regions: ‌ * Newark \(US-East\) * Atlanta \(US-Southeast\) * Toronto \(CA-Central\) * Singapore \(AP-South\) * Mumbai \(AP-West\) * Frankfurt \(EU -Central\) ‌ To effectively address the impact, Akamai restarted the service on route servers in the affected regions between 15:20 UTC and 15:39 UTC on November 21, 2025. The investigation revealed that the new certificates were not loaded on the route servers, leading to unsuccessful queries to the endpoints. Consequently, the route servers were unable to retrieve updates and persisted in operating with outdated data. Multiple products depend on the proper functioning and up-to-date data of the route servers, including: ‌ * Shared IP \(customer peering / failover\) * /56 and /64 ranges * NodeBalancers ‌ The confirmation that all services were operating in accordance with established operational standards was received at 15:48 UTC on November 21, 2025. Following a monitoring period, we validated that the issue had been fully mitigated. ‌ Customers were affected only if they updated the products listed above after the route servers stopped retrieving updates from the Akamai Compute’s internal backend API component. If no changes were made during the impact window, the stale data cached by the route servers remained valid for them. However, any new updates could not be processed due to the failing queries. ‌ Akamai followed the same procedure in unaffected regions to prevent the recurrence of similar issues. Additionally, we will review automated processes and procedures and will implement enhancements in certificate rotations as needed. ‌ We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. ‌ 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.

Read the full incident report →

Started Nov 21, 2025, 11:15 AM UTC· resolved Nov 21, 2025, 08:14 PM UTC

1. investigating Nov 21, 2025, 11:15 AM UTC

   Our team is investigating an emerging service issue affecting Block Storage in all regions. We will share additional updates as we have more information.

2. investigating Nov 21, 2025, 11:30 AM UTC

   Investigation into the recent issue continues. Currently, we recommend users refrain from rebooting Linodes utilizing direct disk boot with encrypted block storage to mitigate potential risk.

3. identified Nov 21, 2025, 05:21 PM UTC

   A recent code-change introduced a bug impacting encrypted block storage volumes configured for direct disk I/O. Customers may experience problems attaching and accessing encrypted volumes to their respective Linodes. If your deployment is configured in this fashion or you believe you may be impacted you can mitigate this by detaching and reattaching your volume to your Linode while it is powered on. Please do not reboot your node with the volume attached as this can result in disk corruption and data loss.

4. monitoring Nov 21, 2025, 06:19 PM UTC

   A recent system update introduced an unexpected behavior impacting encrypted block storage volumes configured for direct disk I/O and we are in the process of rolling back this change. Customers with their deployment(s) configured in this fashion will experience problems attaching and accessing encrypted volumes to their respective Linodes. If you believe you may be impacted by this bug, you can mitigate this behavior by either detaching and reattaching your volume to your Linode while it is powered on, or rebooting your node.

5. resolved Nov 21, 2025, 08:14 PM UTC

   We have finished rolling back the change, and haven’t observed any additional issues with the Block Storage service. We will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

6. postmortem Dec 08, 2025, 04:39 PM UTC

   On November 17th, 2025 at 14:25 UTC, we released an update which introduced an unexpected behavior impacting encrypted Block Storage volumes. Volumes in this configuration could fail to mount if a Linode was rebooted with an encrypted volume attached. Volumes attached to a Linode after boot were unaffected. As a result of this behavior, there was potential for existing data to be overwritten if a volume was written to via direct disk access while in this state. The release was rolled back, mitigating the impact at 18:31 UTC on November 21st. To prevent recurrence of the issue, we are preparing an updated release which will attach encrypted Block Storage volumes correctly at boot. 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.

Read the full incident report →

Started Nov 19, 2025, 08:54 AM UTC· resolved Nov 19, 2025, 12:03 PM UTC

1. investigating Nov 19, 2025, 08:54 AM UTC

   Our team is investigating an emerging service issue where backups are not visible in Cloud Manager. We will share additional updates as we have more information.

2. investigating Nov 19, 2025, 10:17 AM UTC

   We are continuing to investigate an issue where backups are not visible in Cloud Manager. Please note that the backups are not impacted, the issue only affects the visibility. We will share additional updates as we have more information.

3. identified Nov 19, 2025, 11:29 AM UTC

   Our team has identified the issue affecting the Backup visibility in Cloud Manager. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

4. resolved Nov 19, 2025, 12:03 PM UTC

   We haven't observed any additional issues with the Backups in Cloud Manager, 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.

5. postmortem Nov 19, 2025, 12:54 PM UTC

   Starting on November 19, 2025, at approximately 03:39 UTC, a limited number of customers were unable to see their Backups on Cloud Manager. The issue was caused by a planned Cloud Identity and Access Management configuration change that aimed at adding some customers to a Role-Based Access Control \(RBAC\), and did not impact the integrity of the backups. The root cause was identified at approximately 10:00 UTC, and the change was successfully rolled back at 10:42 UTC, at which point the impact was mitigated. To prevent a recurrence, Akamai will review the relevant change procedures to identify potential gaps and make the necessary changes. 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.

Read the full incident report →

Started Nov 18, 2025, 04:45 PM UTC· resolved Nov 18, 2025, 07:17 PM UTC

1. investigating Nov 18, 2025, 04:45 PM UTC

   Our team is investigating a connectivity issue affecting Linode.com and the Community Site. During this time, users may experience connection timeouts and errors when signing in via the Akamai Control Center. We will share additional updates as we have more information.

2. monitoring Nov 18, 2025, 04:55 PM UTC

   At this time we have been able to correct the issue affecting connectivity to Linode.com and the Community Site. We will be monitoring this to ensure that connectivity remains stable. If you continue to experience problems, please open a Support ticket for assistance.

3. resolved Nov 18, 2025, 07:17 PM UTC

   We haven't observed any additional issues with Linode.com or the Community Site, and will now consider this incident resolved. If you are still experiencing additional issues, please open a Support ticket for assistance.

4. postmortem Nov 19, 2025, 02:35 PM UTC

   On November 18, 2025, at approximately 15:50 UTC, customers experienced errors when accessing [cloud.linode.com](http://cloud.linode.com) via Akamai Control Center, even after authentication. ‌ Akamai was aware of the issue via the alerting system, and we commenced restoring our services without delay. Access to the Akamai Control Center and the login to [cloud.linode.com](http://cloud.linode.com) were restored at approximately 16:45 UTC. After a period of systematic monitoring, we verified that the issue had been effectively mitigated. ‌ Our investigation indicated that the issue originated from a script executed to clean up certain data. However, this script had an adverse effect in production, leading to the observed customer impact. ‌ To prevent a similar issue in the future, Akamai has stopped running such scripts and will conduct an audit to ensure no other scripts cause similar issues. Additionally, we will do an in-depth analysis and implement any improvements in our change strategies. ‌ 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.

Read the full incident report →

Started Nov 18, 2025, 06:19 AM UTC· resolved Nov 19, 2025, 04:49 AM UTC

1. investigating Nov 18, 2025, 06:19 AM UTC

   Our team is investigating an issue affecting connectivity in our US-ORD (Chicago) 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.

2. investigating Nov 18, 2025, 07:35 AM UTC

   The investigation revealed that the issue is caused due to internal network connectivity. Due to this issue, Compute services/applications hosted in this data center will experience 5xx errors and timeouts. We are actively working on mitigation steps. We will provide the next update as we make progress.

3. investigating Nov 18, 2025, 08:47 AM UTC

   We are continuing to investigate this issue. Subsequent updates will be provided as we make progress.

4. investigating Nov 18, 2025, 09:18 AM UTC

   Our team has identified the issue affecting connectivity in our US-ORD (Chicago) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

5. monitoring Nov 18, 2025, 10:10 AM UTC

   At this time, we have been able to correct the issues affecting connectivity in our US-ORD (Chicago) 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.

6. monitoring Nov 18, 2025, 01:09 PM UTC

   We are continuing to monitor. If you are still experiencing issues, please open a Support ticket for assistance.

7. resolved Nov 19, 2025, 04:49 AM UTC

   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.

8. postmortem Nov 21, 2025, 01:10 AM UTC

   Starting around 03:05 UTC on November 18, 2025, the US-ORD \(Chicago\) datacenter \(DC\) started having network connectivity issues that led to intermittent packet loss. The Compute Object Storage service was impacted as a result. The proactive monitoring system detected this issue, triggering the internal alerts. The investigation revealed that the issue was caused due to an ASIC failure corrupting the forwarding table in one of the network routers in this DC. The problematic network router was isolated to mitigate the impact. The issue was mitigated at around 08:46 UTC on November 18, 2025. Akamai replaced the faulty network router and brought the network router into production service. We monitored the traffic after this step and confirmed that the services are restored and working as expected after replacing the network router. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. 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.

Read the full incident report →

Started Nov 14, 2025, 01:11 AM UTC· resolved Nov 14, 2025, 04:49 AM UTC

1. investigating Nov 14, 2025, 01:11 AM UTC

   Our team is investigating an emerging service issue affecting the Linode API. We will share additional updates as we have more information.

2. investigating Nov 14, 2025, 02:17 AM UTC

   We have identified a service issue affecting the Linode Cloud Manager and API. While we work to resolve this issue, the Linode Cloud Manager and API may be intermittently unavailable across all regions, and operations through the Linode API, including certain Linode Kubernetes Engine (LKE) operations like auto-scaling, may fail. Customers will be unable to open Akamai Cloud Support tickets while the Linode API remains unavailable. We are actively working to restore normal service and will provide additional updates as we make progress.

3. investigating Nov 14, 2025, 03:16 AM UTC

   We are continuing to work on mitigating this issue. We have restored partial Cloud Manager and API functionality. Operations through the Linode Cloud Manager and API, including LKE operations like auto-scaling, may intermittently hang or fail until service has been fully restored. We will share additional updates as we have more information.

4. monitoring Nov 14, 2025, 03:51 AM UTC

   We have mitigated the issue affecting the Linode Cloud Manager and API. We will be monitoring this issue 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].

5. resolved Nov 14, 2025, 04:49 AM UTC

   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.

6. postmortem Nov 17, 2025, 10:32 AM UTC

   Starting around 01:01 UTC on November 14, 2025, Compute customers were intermittently unable to access [Linode Cloud Manager](https://cloud.linode.com/) and operations involving the Linode API, including certain Linode Kubernetes Engine \(LKE\) operations like auto-scaling were failing. Akamai’s proactive monitoring system detected this issue, triggering the internal alerts. During the preliminary investigation, Akamai observed failures in Linode's hosting database \(DB\). Further investigation determined that the issue was caused due to a high volume of concurrent connections and long-running queries in the primary DB. As part of the mitigation effort, we have manually killed the concurrent connections and long-running queries in the primary DB. Following these actions, the impact was mitigated at around 03:20 UTC on November 14, 2025. We will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. If you need further assistance, please [open a support ticket](https://cloud.linode.com/support/tickets) or call us at 855-454-6633 \(\+1-609-380-7100 Intl.\), or send an email to [[email protected]](mailto:[email protected]). 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.

Read the full incident report →

Started Nov 08, 2025, 05:08 PM UTC· resolved Nov 14, 2025, 12:59 PM UTC

1. monitoring Nov 08, 2025, 05:08 PM UTC

   On November 8 2025, customers using services hosted in our Mumbai (in-bom-2) and Chennai (in-maa) datacenters may have experienced packet loss and connection timeouts due to an issue with a third party transit provider. We are working with the provider to determine the cause of the issue. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

2. resolved Nov 14, 2025, 12:59 PM UTC

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

Read the full incident report →