Networking in SFO3 and AMS3 regions

lowDigitalOceanSep 29, 2025 13:300

networkstoragesecurity

Network / RoutingSecurity IncidentStorage Failure

Summary

From 05.45 to 9.20 UTC, our Engineering team observed a Networking issue in the SFO3 and AMS3 region related to DDoS mitigation workflows. During this time, a subset of Droplets remained in protective filtering longer than intended due to a monitoring issue in AMS3 that caused a small number of IPs to stay blocked incorrectly. Users should no longer be experiencing these issues. We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via

Impact

none

Timeline

Sep 29, 2025 13:30

[resolved] From 05.45 to 9.20 UTC, our Engineering team observed a Networking issue in the SFO3 and AMS3 region related to DDoS mitigation workflows. During this time, a subset of Droplets remained in protective filtering longer than intended due to a monitoring issue in AMS3 that caused a small number of IPs to stay blocked incorrectly. Users should no longer be experiencing these issues. We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.

via statuspage

Lessons Learned

⚠DigitalOcean has experienced 46 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to network, storage, security have occurred 52 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, Security Incident, Storage Failure. Consider implementing preventive measures specific to this failure category.