WhatBrokeToday
GTA 6FAQ

GitLab vs Render: reliability

In the last 60 days, GitLab 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

GitLab and Render reliability over the last 60 days
MeasureGitLabRender
Incidents (60 days)1411
Critical or high42
Median time to fix1 min1 min
Longest incident1 min18 min
Never on its status page50
Status page delay (median)1 min1 min
30-day hazard rating4.7 / 104.3 / 10

GitLab's worst incidents

GitLab's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
GitLab Backup Procedure Fails Due to PostgreSQL Major Version Mismatch

Cause: A difference in major versions between pg_dump (9.2) and the running PostgreSQL database (9.6) caused pg_dump to produce an error and end the backup.

highongoingnot yet
GitLab: Issues Running Pipelineshigh1 minfirst
GitLab Security Incident: Attempted Exploitation of CVE-2026-97229high1 minnever
GitLab Outagehighongoingnot yet
GitLab: CI/CD Job Delays on GitLab.commedium1 minfirst
Full GitLab 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