Droplets (CPU) SLADigitalOcean · Compute · DigitalOcean · Compute
Promise vs reality
Downtime used against the allowance
0 min of major incidents53 min allowed in 365 days
0 major and 0 minor incidents. 0 min degraded (not counted).
Major incident minutes per month
Allowed per month: 4.4 min
- Promised
- 99.99%
- Observed, 365d
- 100%
- Major incident time
- 0 min
- Credit on first breach
- 100%
Commitments and credits
- All Droplets (instance-level)Each individual Droplet instance99.99%
Monthly uptime below, credit of the bill
- Below 99.99%100%
Terms
- Measured
- Per individual Droplet: (minutes in month - minutes of Unavailability) / minutes in month
- Credit cap
- Credits apply only to charges for the affected Droplet resources
- Claim window
- Within two (2) billing cycles of the month when the downtime occurred
- How to claim
- Email success@digitalocean.com with account email, affected Droplet and outage times
Not covered
- Scheduled maintenance or customer-initiated downtime
- Factors beyond DigitalOcean's reasonable control (force majeure, third-party outages)
- Account restrictions, misuse, or violation of the Customer Agreement
- Customer application code or configuration errors
DigitalOcean commits to a Monthly Uptime Percentage of 99.99% for each individual Droplet instance.
Single-step schedule: less than 99.99% = 100% credit of the affected Droplet's charges. DOKS control plane and DBaaS are covered by their own SLAs.
Evidence: incidents, last 365 days
No incidents on file for this service.
Other compute SLAs
ServiceDowntime vs allowed
Amazon EC2AWS99.99% / 99.178%
Cloudflare WorkersCloudflare99.99% / 100%
Confluent Cloud for Apache FlinkConfluent99.99% / 99.628%
Droplets (CPU)DigitalOcean99.99% / 100%
Compute EngineGoogle Cloud99.99% / 99.927%
Azure FunctionsMicrosoft Azure99.95% / n/a
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.