CompaniesLinode (Akamai)Incidents
Linode (Akamai): Service Issue - Object Storage
Timeline of updates
- resolved
We identified an issue with our Object Storage service in our Washington, DC (us-iad) data center. Users may have experienced high latency between 00:00 UTC to 15:30 UTC January 25, 2024. We pinpointed the cause of the issue and have took steps to mitigate the cause of the latency as of 15:30 UTC on January 25, 2024. Based on current observations, Object Storage in Washington, DC has resumed normal operations. We haven’t observed any additional issues with the Object Storage service, and consider this incident resolved. If you continue to experience problems, please 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 2024-01-25 18:04 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Issue - Object Storage
- Vendor
- Linode (Akamai)
- Date
- URL
- https://rewindex.com/company/linode-akamai/incidents/lfjjbm2jk9wm
Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on January 25, 2024Linode (Akamai) in January 2024MarkdownJSON