Block Storage Volume NYC1 and NYC3
Summary
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.
Impact
minor
Timeline
[investigating] Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1 and NYC3 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.
via statuspage[investigating] 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.
via statuspage[investigating] We are continuing to investigate this issue.
via statuspage[investigating] We are continuing to investigate this issue.
via statuspage[monitoring] 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.
via statuspage[resolved] 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.
via statuspageLessons Learned
⚠DigitalOcean has experienced 94 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, storage have occurred 173 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Network / Routing, Storage Failure. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Networking in BLR1
DigitalOcean · Jul 19, 2026
Some users are unable to access Codex
OpenAI · Jul 18, 2026
Network Performance Issues in Paris, France (CDG)
Cloudflare · Jul 17, 2026
Network Performance Issues for AWS ap-northeast-1 region
Cloudflare · Jul 17, 2026
Copilot Coding Agent Degraded Job Completion
GitHub · Jul 16, 2026