What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Linode now? Check the current statusUpdates (2)
- Jun 24, 2026, 05:39 PMService Issue - Debian Package Availability
Our upstream third-party Debian repo failed to sync with their own upstream repo chain for an unknown reason. The InRelease files for Debian packages were left to expire starting at approximately 08:12 UTC on June 24, 2026, preventing any Debian packages from getting installed. We didn't have programmatic visibility at that time to know that these files were unable to download or if the expiration date in the InRelease files had been reached. We mitigated the issue at approximately 12:35 UTC on June 24, 2026, by updating which repo we are syncing Debian packages from and purging the stale InRe
Linode ↗ - Jun 24, 2026, 04:27 PMService Issue - Debian Package Availability
Between approximately 08:12 UTC and 12:35 UTC on June 24, 2026, attempting to create/autoscale Linodes using a Debian distribution may have failed due to a stale InRelease file in an upstream repository. We have mitigated the issue by updating our mirror endpoint to a healthy repository. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Linode ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Linode's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.