CompaniesLinode (Akamai)Incidents
Linode (Akamai): Service Issue - Block Storage US-ORD (Chicago), US-IAD (Washington, D.C.)
Timeline of updates
- resolved
From Jan 15 at 11:00 AM UTC to Jan 16 at 3:30 PM UTC, customers may have encountered issues when cloning Block Storage volumes. We have since corrected the underlying problems affecting the Block Storage service, and customers are encouraged to reattempt their clone operations. We will continue to monitor the service closely to ensure ongoing stability. If you experience any further issues, please don't hesitate to open a Support ticket for assistance.
From Linode (Akamai)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.linode.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Linode (Akamai), started 2025-01-15 11:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Issue - Block Storage US-ORD (Chicago), US-IAD (Washington, D.C.)
- Vendor
- Linode (Akamai)
- Date
- URL
- https://rewindex.com/company/linode-akamai/incidents/cq8qtvfb49sh
Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on January 15, 2025Linode (Akamai) in January 2025MarkdownJSON