WhatBrokeToday
GTA 6FAQ

PostgreSQL vs Supabase: reliability

In the last 60 days, PostgreSQL had 7 incidents and Supabase had 40 incidents (median fix 1 min). PostgreSQL broke less often.

Side by side, last 60 days

PostgreSQL and Supabase reliability over the last 60 days
MeasurePostgreSQLSupabase
Incidents (60 days)740
Critical or high33
Median time to fixn/a1 min
Longest incidentn/a26 h
Never on its status pagen/a0
Status page delay (median)n/a1 min
30-day hazard rating5.6 / 108.3 / 10

PostgreSQL's worst incidents

PostgreSQL's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
PostgreSQL Multiple High-Severity Vulnerabilities (CVE-2026-116304 through CVE-2026-116325)

Cause: Type confusion, use-after-free, heap-based buffer overflow, improper protection of alternate paths, untrusted search path issues, improper input validation, and SQL injection across various PostgreSQL internal components and utilities.

highongoing
PostgreSQL 22-Year-Old Type-Confusion Primitive Turned into Remote Code Execution

Cause: A type-confusion primitive present for 22 years was exploited to achieve remote code execution.

highongoing
Postgres recovery_prefetch can cause outages

Cause: recovery_prefetch feature misbehaved during recovery process

highongoing
Postgres Lock Queue Migration Outage Discussionmediumongoing
PostgreSQL Primary Cancel Commits Impact Async Replica Lag

Cause: The async replica database was lagging behind the PostgreSQL primary, causing read operations to access stale data.

mediumongoing
Full PostgreSQL outage history

Supabase's worst incidents

Full Supabase outage history