DigitalOcean incident history

Right now: clear, by DigitalOcean's own status page, mirrored every five minutes.

50
incidents kept since 22 Apr 2026
2
in the last 30 days
2h 38m
median time to resolve, once posted
20%
resolved within an hour

How far back this goes: DigitalOcean's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 156 days so far and grows from here. Impact labels (8 major or critical) are DigitalOcean's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares DigitalOcean as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind DigitalOcean are watched.

Which parts of DigitalOcean the incidents touched

Global
14
Agent Runtime
7
Inference
6
Cloud Control Panel
5
NYC3
4
DNS
4

Every incident we hold, newest first

16 Sept 2026
minor
11h 21m
24 Aug 2026
critical
1d 1h
23 Aug 2026
minor
9h 21m
19 Aug 2026
critical
8h 24m
6 Aug 2026
minor
2h 3m
4 Aug 2026
minor
5h 29m
3 Aug 2026
minor
4h 1m
19 Jul 2026
minor
2h 54m
16 Jul 2026
minor
3h 44m
9 Jul 2026
minor
1d 4h
4 Jul 2026
none
27m 18s
2 Jul 2026
minor
10h 15m
1 Jul 2026
none
2h 14m
27 Jun 2026
none
—
4 Jun 2026
minor
1h 34m
29 May 2026
minor
7h 44m
20 May 2026
minor
54m 43s
20 May 2026
minor
2h 12m
8 May 2026
minor
1h 58m
23 Apr 2026
minor
2h 1m
23 Apr 2026
minor
1h 44m
22 Apr 2026
minor
40m 48s

Source: DigitalOcean's public status page at status.digitalocean.com, mirrored every five minutes. Data as JSON: /upstream/digitalocean/incidents.json. CC BY 4.0.

If your site depends on DigitalOcean, Repose holds the page when the cause is upstream. How the hold decision works →