WhatBrokeToday
GTA 6FAQ

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 and Render reliability over the last 60 days
MeasureCircleCIRender
Incidents (60 days)1411
Critical or high22
Median time to fix1 min1 min
Longest incident1 min18 min
Never on its status page00
Status page delay (median)1 min1 min
30-day hazard rating2.7 / 104.3 / 10

CircleCI's worst incidents

CircleCI's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
CircleCI: Delay in data appearing in UI and APIhigh1 minfirst
CircleCI: Delays in pipelines, workflows, UI data, and notificationshigh1 minfirst
CircleCI: Increased wait time for Machine and Remote Docker jobs

Cause: Increased usage leading to capacity constraints for Machine and Remote Docker jobs.

medium1 minfirst
CircleCI: Delays for gen2 dedicated IP range jobs

Cause: Limited compute availability from the cloud provider

medium1 minfirst
CircleCI: Increased Docker gen2 wait timesmedium1 minfirst
Full CircleCI outage history

Render's worst incidents

Render's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
Render: Builds, deploys, and queued deploys are not starting in all regionshigh1 minfirst
Render: Build and deploy failures in Oregonhigh1 minfirst
Render: API Performance Issuesmedium18 minfirst
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.

medium1 minfirst
Render: Degraded network performancemedium1 minfirst
Full Render outage history