CompaniesLinode (Akamai)Incidents
Linode (Akamai): Service Issue - Object Storage - US-MIA (Miami)
Timeline of updates
- resolved
Our team has identified an issue affecting the Object Storage service between approximately 21:30 UTC on January 30, 2025, and 01:30 UTC on January 31, 2025. During this time, users may have experienced 403 errors. We have implemented a fix as of 01:30 UTC, on January 31, 2025, and haven't observed any additional issues with the Object Storage service since. 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 2025-01-30 20:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Issue - Object Storage - US-MIA (Miami)
- Vendor
- Linode (Akamai)
- Date
- URL
- https://rewindex.com/company/linode-akamai/incidents/22tkxfz6v2v2
Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on January 30, 2025Linode (Akamai) in January 2025MarkdownJSON