Resolved incident

Emerging Service Issue - Cloud Manager

Linode · None · Started

Duration
1h 23m
Severity
None
Status
Postmortem

Summary

None · Postmortem

On July 9, 2026, at 15:43 UTC, customers were unable to login to [cloud.linode.com](http://cloud.linode.com) using username and password. Customers were getting "wrong password" error message.  Investigation revealed that the issue was due to an internal certificate issue. To mitigate the impact, we fixed the certificate issue on the impacted servers at 17:24 UTC on July 9, 2026. After monitoring our systems for some time, we confirmed the issue was fully resolved. Akamai will deploy a permanent fix to prevent a recurrence of the issue.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Investigating

    Linode

    Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.

  2. Investigating

    Linode

    We are continuing to investigate this issue. We will provide an update within the next 30 minutes.

  3. Monitoring

    Linode

    At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.

  4. Resolved

    Linode

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

  5. Postmortem

    Linode

    On July 9, 2026, at 15:43 UTC, customers were unable to login to [cloud.linode.com](http://cloud.linode.com) using username and password. Customers were getting "wrong password" error message.  Investigation revealed that the issue was due to an internal certificate issue. To mitigate the impact, we fixed the certificate issue on the impacted servers at 17:24 UTC on July 9, 2026. After monitoring our systems for some time, we confirmed the issue was fully resolved. Akamai will deploy a permanent fix to prevent a recurrence of the issue.