CompaniesDigitalOceanIncidents
DigitalOcean: Block Storage in SFO3
Timeline of updates
- resolved
Our Engineering team is investigating an issue related to our ongoing SFO3 maintenance here: https://status.digitalocean.com/incidents/4kj7krrpyg3k (opens in new tab) From 20:23 - 20:25 UTC, some services were impacted by a drop in networking. During that time, some Managed Kubernetes clusters experienced errors from the Kubernetes API and/or an increase in 5xx errors. Communication between other services and Block Storage Volumes may have been impacted as well. The impact has been mitigated and services should be working normally at this time. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
From DigitalOcean’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.digitalocean.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by DigitalOcean, started 2024-11-25 22:05 UTC, resolved after 0 min, 1 update(s).
- Title
- Block Storage in SFO3
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/nz9lwl328ppy
DigitalOcean profileRecent DigitalOcean incidentsAll outages on November 25, 2024DigitalOcean in November 2024MarkdownJSON