CompaniesDigitalOceanIncidents
DigitalOcean: Container Registry in Multiple Regions
Timeline of updates
- resolved
From 23:16 - 04:00, updates to DigitalOcean Container Registry images were not displayed correctly in the UI (Cloud Control Panel), due to a lapsed internal authorization token. Our Engineering team was able to issue a new token and rolled out the change regionally in order to not disrupt multiple data planes at once. This issue is fully resolved. If you continue to experience problems, please open a ticket with our Support team. Thank you for your patience and we apologize for the 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 2023-08-12 02:09 UTC, resolved after 2.3 h, 1 update(s).
- Title
- Container Registry in Multiple Regions
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/45pv9lj0zj1v
DigitalOcean profileRecent DigitalOcean incidentsAll outages on August 12, 2023DigitalOcean in August 2023MarkdownJSON