CompaniesDigitalOceanIncidents
DigitalOcean: Container Registry in SFO3
Timeline of updates
- resolved
Our Engineering team has identified the root cause of the incident to be multiple DB calls causing DB contention. During this time, users might have experienced issues interacting and authenticating with the DigitalOcean Container Registry, creating new container registries, and pushing/deleting images to/from registries. As of 00:10 UTC, we have confirmed the full resolution of the issue affecting the DigitalOcean Container Registry in the SFO3 region. We appreciate your patience throughout the process and if you continue to experience problems, please open a ticket with our support team for further review.
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: minor) posted by DigitalOcean, started 2023-05-24 19:28 UTC, resolved after 7.3 h, 1 update(s).
- Title
- Container Registry in SFO3
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/mmngtxzmm6gs
DigitalOcean profileRecent DigitalOcean incidentsAll outages on May 24, 2023DigitalOcean in May 2023MarkdownJSON