CompaniesDigitalOceanIncidents
DigitalOcean: Networking in SFO3 and AMS3 regions
Timeline of updates
- 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.
From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by DigitalOcean, started 2025-09-29 13:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Networking in SFO3 and AMS3 regions
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/zgc7tnzs04g1
DigitalOcean profileRecent DigitalOcean incidentsAll outages on September 29, 2025DigitalOcean in September 2025MarkdownJSON