CompaniesDigitalOceanIncidents
DigitalOcean: Multiple Services Disruption
Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents
DigitalOcean’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +56 min vs the first vendor naming Cloudflare)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
root --> h4
later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
root --> later
me["DigitalOcean (this incident)<br/>posted +56 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Our Engineering team has confirmed that the external network incident affecting multiple DigitalOcean services has been fully mitigated. The impacted services including Gen AI tools, App Platform, Load Balancers, Spaces, and provisioning or management actions for new clusters have recovered and are now operating normally. All requests are completing successfully. Thank you for your patience. If you continue to experience any issues, please open a support ticket from within your account.
From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).
DigitalOcean profileRecent DigitalOcean incidentsMarkdownJSON