DigitalOcean incident: Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1

Affected components

• BLR1
• NYC1
• NYC3
• SGP1
• SYD1

1. resolvedJul 19, 2026, 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.

2. monitoringJul 19, 2026, 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.

3. investigatingJul 19, 2026, 13:36 UTC

   We are continuing to investigate this issue.

4. investigatingJul 19, 2026, 13:34 UTC

   We are continuing to investigate this issue.

5. investigatingJul 19, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in DigitalOcean's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [GRA11][Compute - Instance] - Instance creation incident notificationMajor · Jul 19, 2026, 13:26 UTC
• OVHcloud: [GRA][AI & Machine Learning] - AI Deploy/Training/Notebooks incident notificationMajor · Jul 19, 2026, 14:27 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Twilio: SMS Delivery Failures from Twilio to Vodafone AustraliaMinor · Jul 13, 2026, 02:47 UTC
• Grafana Cloud: Issue with Dashboard Views Being RegisteredMinor · Jul 14, 2026, 08:10 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Long Codes to Chunghwa TaiwanMinor · Jul 17, 2026, 14:10 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Reliance Jio IndiaMinor · Jul 17, 2026, 15:54 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Pelephone IsraelMinor · Jul 18, 2026, 15:05 UTC
• Twilio: User Authentication Identity Gateway API Failure Increase in CanadaMinor · Jul 19, 2026, 04:33 UTC

How often does DigitalOcean have incidents?

DigitalOcean reported 20 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 5h 35m. See DigitalOcean's uptime and incident history