Resolved incident
Service Issue - Debian Package Availability
Linode · None · Started
- Duration
- < 1m
- Severity
- None
- Status
- Postmortem
Summary
None · Postmortem
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 InRelease files from our cache. We are working to integrate system visibility and alerting around expiration dates of these files in addition to switching to a more reliable upstream repo, i.e. Debian's official repos. 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.
Event timeline
How this incident unfolded, from the official status page.
Resolved
Linode
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.
Postmortem
Linode
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 InRelease files from our cache. We are working to integrate system visibility and alerting around expiration dates of these files in addition to switching to a more reliable upstream repo, i.e. Debian's official repos. 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.