Container Registry in Multiple Regions
Incident
Report for DigitalOcean
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.
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.
Monitoring
Our Engineering team has confirmed the root cause of the issue with updates to the UI for DigitalOcean Container Registry and a fix is now rolling out regionally.
As this rolls out, we expect users to once again be able to see updates to Container Registry images in the UI (Cloud Control Panel).
We will post another update once the fix finishes rolling out in all regions.
As this rolls out, we expect users to once again be able to see updates to Container Registry images in the UI (Cloud Control Panel).
We will post another update once the fix finishes rolling out in all regions.
Identified
From 23:16 UTC, our Engineering team has identified an issue with DigitalOcean Container Registry and is actively working on a fix. During this time, customers will not be able to see changes on UI for new DOCR Images in multiple regions. We will post an update as soon as additional information is available.
This incident affected: Container Registry (AMS3, FRA1, NYC3, SFO3, SGP1, SYD1).