DigitalOcean vs Render: reliability
In the last 60 days, DigitalOcean had 6 incidents (median fix 1 min) and Render had 11 incidents (median fix 1 min). DigitalOcean broke less often.
Side by side, last 60 days
| Measure | DigitalOcean | Render |
|---|---|---|
| Incidents (60 days) | 6 | 11 |
| Critical or high | 1 | 2 |
| Median time to fix | 1 min | 1 min |
| Longest incident | 1 min | 18 min |
| Never on its status page | 1 | 0 |
| Status page delay (median) | 1 min | 1 min |
| 30-day hazard rating | 2.7 / 10 | 4.3 / 10 |
DigitalOcean's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| DigitalOcean: Kubernetes Cluster Management Operations | high | 1 min | first | |
| DigitalOcean: DNS Resolution for Managed Kubernetes | medium | 1 min | first | |
| DigitalOcean: VPC Networking Availability | medium | 1 min | first | |
| DigitalOcean: App Platform Accessibility in Cloud Panel | minor | 1 min | first | |
| Dreamhost: Investigating an incident affecting File Manager and Webmail | minor | 1 min | never |
Render's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Render: Builds, deploys, and queued deploys are not starting in all regions | high | 1 min | first | |
| Render: Build and deploy failures in Oregon | high | 1 min | first | |
| Render: API Performance Issues | medium | 18 min | first | |
| Render: Issues affecting connections to a subset of Postgres Databases Cause: A configuration change rolled out to a small subset of Postgres instances caused connection failures for databases routing traffic through self-managed PgBouncer instances. | medium | 1 min | first | |
| Render: Degraded network performance | medium | 1 min | first |