Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1
Jul 19, 09:51 UTCJul 19, 15:32 UTC
Duration
5h 41m
Impact
Minor
Root cause
Storage
DigitalOcean, 90 days
30 incidents
Affected
BLR1NYC1NYC3SGP1SYD1Volumes - BLR1Volumes - NYC1Volumes - NYC3Volumes - SGP1Volumes - SYD1
Final update
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
Timeline
- Resolved · Jul 19, 15:32 UTC
Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally. If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
- Monitoring · Jul 19, 14:52 UTC
Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.
- Investigating · Jul 19, 13:36 UTC
We are continuing to investigate this issue.
- Investigating · Jul 19, 13:34 UTC
We are continuing to investigate this issue.
- Investigating · Jul 19, 09:51 UTC
Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.
More from DigitalOcean
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1609:48 UTC | Support Portal Service Disruption | minor | 11h 21m |
| Sep 910:47 UTC | Power Degradation impacting GPU Performance in ATL1 | minor | 1h 38m |
| Aug 2417:14 UTC | Cloud Control Panel and API | critical | 25h 50m |
| Aug 2305:11 UTC | Managed Databases Creation | minor | 9h 22m |
| Aug 2112:59 UTC | Container Registry and Spaces Accessibility | minor | 1h 53m |
| Aug 1911:10 UTC | Major Service Interruption in MKC1 | critical | 8h 25m |
Also caused by storage
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1715:50 UTC | AutoOps node metrics temporarily unavailable in some regions | major | 41m | |
| Sep 1015:26 UTC | Unresponsive Projects | major | 27h 40m | |
| Aug 2623:37 UTC | Disruption with GitHub Billing | minor | 20h 7m | |
| Aug 2413:56 UTC | Actions delays in starting runs | minor | 38m | |
| Aug 1316:21 UTC | Disruption with GHEC Team Sync | minor | 2h 6m | |
| Jun 1119:42 UTC | Incident with Webhooks | minor | 2h 37m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.