CircleCI vs Render: reliability
In the last 60 days, CircleCI had 14 incidents (median fix 1 min) and Render had 11 incidents (median fix 1 min). Render broke less often.
Side by side, last 60 days
CircleCI's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| CircleCI: Delay in data appearing in UI and API | high | 1 min | first | |
| CircleCI: Delays in pipelines, workflows, UI data, and notifications | high | 1 min | first | |
| CircleCI: Increased wait time for Machine and Remote Docker jobs Cause: Increased usage leading to capacity constraints for Machine and Remote Docker jobs. | medium | 1 min | first | |
| CircleCI: Delays for gen2 dedicated IP range jobs Cause: Limited compute availability from the cloud provider | medium | 1 min | first | |
| CircleCI: Increased Docker gen2 wait times | medium | 1 min | first |
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 |