Live / Linode / Incident
Linode: Service Issue - Cloud Manager and API
Linode · linode.comMinor incidentResolved2026-10-13 08:03 UTC
Public — what happened
Summary
Linode said that on 2026-10-09 at 03:43 UTC it had found a problem with signing in to Cloud Manager, where some customers were not getting the verification codes needed to log in. The company did not say what caused it. By 05:23 UTC the same day, Linode reported the login problem had been corrected and it was watching to make sure things stayed stable. The incident was marked resolved on 2026-10-13 at 08:03.
Affected
Cloud Manager and API
Timeline
- Started — 2026-10-09 03:43 UTC
- Identified — 2026-10-09 03:43 UTC
- Monitoring — 2026-10-09 05:23 UTC
- Resolved — 2026-10-13 08:03 UTC · 4 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Linode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Linode: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Linode report →
More from Linode
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.