Linode Status

Postmortem: 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). The investigation revealed that the issue was caused by an internal certificate expiry for the 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.

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

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

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

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

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

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

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

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

Resolved: We became aware of an issue that affected connectivity in our FR-PAR (Paris), FR-PAR-2 (Paris 2), and ES-MAD (Madrid) data centers. The issue lasted between 21:25 UTC and 22:50 UTC on February 17, 2026, and between 11:44 UTC and 12:16 UTC on February 18, 2026. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in those data centers. We can confirm that the issue has been resolved and service has resumed normal operations. If you continue to experience problems, please open a Support ticket for assistance.

Resolved: We became aware of an issue that affected connectivity in our FR-PAR (Paris), FR-PAR-2 (Paris 2), and ES-MAD (Madrid) data centers. The issue lasted between 21:25 UTC and 22:50 UTC on February 17, 2026, and between 11:44 UTC and 12:16 UTC on February 18, 2026. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in those data centers. We can confirm that the issue has been resolved and service has resumed normal operations. If you continue to experience problems, please open a Support ticket for assistance.

Resolved: We became aware of an issue that affected connectivity in our FR-PAR (Paris), FR-PAR-2 (Paris 2), and ES-MAD (Madrid) data centers. The issue lasted between 21:25 UTC and 22:50 UTC on February 17, 2026, and between 11:44 UTC and 12:16 UTC on February 18, 2026. During this time, users may have experienced intermittent connection timeouts and errors for all services deployed in those data centers. We can confirm that the issue has been resolved and service has resumed normal operations. If you continue to experience problems, please open a Support ticket for assistance.

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

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