checked Sep 21, 2026 10:43 AM UTC · Linode's official status page
Linode is up and running.
All components operational
Statusfield watches Linode alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
7 reports published by Linode in the last 30 days · 1 still open
When Linode breaks, it is typically resolved in 1h 50m — median across 10 resolved incidents over 90 days.
ScheduledSep 15 · 21:00 UTC
Power maintenance is being conducted within our ORD2 (Chicago) datacenter between 11:00 UTC and 21:00 UTC on September 15th, 2026. No downtime or impact is expected as backup power is available for all services within this region. If you have questions surrounding this maintenance please open a Support ticket from the Linode Manager."
Reported by Linode on their status page.
postmortemSep 8 · 09:26 UTC
Between approximately 10:15 and 12:18 UTC on September 7, 2026, customers could have experienced elevated error rates and 5xx response codes when using Cloud Manager or performing API calls. The investigation revealed that the issue started due to increased API load that over-utilized our database resources which in turn led to the symptoms seen by users. To mitigate the issue, the team addressed the elevated API load issue which brought back utilization of our resources within normal ranges. Ongoing actions include monitoring platform stability, and planning enhancements to API rate limiting. 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.
Reported by Linode on their status page.
ResolvedSep 7 · 13:31 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 support@linode.com for assistance.
Reported by Linode on their status page.
postmortemAug 28 · 20:36 UTC
Between approximately 09:51 and 12:18 UTC on August 28, 2028, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected. The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled. This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 12:18 UTC on August 28, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues 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.
Reported by Linode on their status page.
CompletedSep 15 · 02:09 UTC
This maintenance has been cancelled and will not take place during the scheduled window. No changes were made and no impact to services is expected. If you have questions, please open a Support ticket from the Cloud Manager.
Reported by Linode on their status page.
resolvedAug 25 · 01:11 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.
Reported by Linode on their status page.
postmortemSep 7 · 18:36 UTC
On August 21, 2026 starting approximately at 17:23 UTC, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected. The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled. This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 21:59 UTC on August 21, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues 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.
Reported by Linode on their status page.
