Render vs Vercel: reliability
In the last 60 days, Render had 11 incidents (median fix 1 min) and Vercel had 9 incidents (median fix 1 min). Vercel broke less often.
Side by side, last 60 days
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 |
Vercel's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Vercel: Delays in observability data | high | 3 h | first | |
| Vercel: Increased build and deployment failures | high | 1 min | first | |
| Vercel: Delays in Drains, Observability, and Workflow in Washington (iad1) | high | 1 min | first | |
| Vercel Auth login failures for pages with Deployment Protection enabled | high | 1 min | first | |
| Vercel: Elevated Sandbox and Blob request latency and errors | medium | 4 min | first |