Container Registry SLADigitalOcean · Developer tools · DigitalOcean · Developer tools
Promise vs reality
Downtime used against the allowance
0 min of major incidents4.4 h allowed in 365 days
0 major and 0 minor incidents. 0 min degraded (not counted).
Major incident minutes per month
Allowed per month: 22 min
- Promised
- 99.95%
- Observed, 365d
- 100%
- Major incident time
- 0 min
- Credit on first breach
- 10%
Commitments and credits
- AllContainer Registry images99.95%
Monthly uptime below, credit of the bill
- Below 99.95%10%
- Below 99%25%
- Below 95%100%
Terms
- Measured
- 100% minus share of 5-minute intervals with no push/pull accessibility
- Claim window
- Within 30 days of the end of the billing cycle
- How to claim
- Contact Support
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
During each billing cycle, the Container Registry will have 99.95% Uptime (as defined below) per month
Credits usable within 90 days.
Evidence: incidents, last 365 days
No incidents on file for this service.
Other developer tools SLAs
ServiceDowntime vs allowed
Confluence (Cloud)Atlassian99.95% / n/a
Jira (Cloud)Atlassian99.95% / 99.403%
Jira Product Discovery (Cloud)Atlassian99.95% / n/a
Jira Service Management (Cloud)Atlassian99.95% / n/a
Container RegistryDigitalOcean99.95% / 100%
Bitbucket Cloud (Cloud)Atlassian99.9% / n/a
Compass (Cloud)Atlassian99.9% / n/a
GitHub ActionsGitHub99.9% / 99.117%
GitHub Enterprise CloudGitHub99.9% / 99.172%
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.