Linode incident

Service Issue - Cloud Manager and API

Minor Resolved View vendor source →

Linode experienced a minor incident on September 7, 2026 affecting Cloud Manager and API, lasting 2h 52m. The incident has been resolved; the full update timeline is below.

Started
Sep 07, 2026, 10:38 AM UTC
Resolved
Sep 07, 2026, 01:31 PM UTC
Duration
2h 52m
Detected by Pingoru
Sep 07, 2026, 10:38 AM UTC

Affected components

Cloud Manager and API

Update timeline

  1. investigating Sep 07, 2026, 10:38 AM UTC

    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.

  2. investigating Sep 07, 2026, 11:39 AM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 07, 2026, 12:12 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Sep 07, 2026, 01:27 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].

  5. resolved Sep 07, 2026, 01:31 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.

  6. postmortem Sep 08, 2026, 09:26 AM 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.