WhatBrokeToday
GTA 6FAQ

MongoDB vs Supabase: reliability

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

Side by side, last 60 days

MongoDB and Supabase reliability over the last 60 days
MeasureMongoDBSupabase
Incidents (60 days)840
Critical or high53
Median time to fix1 min1 min
Longest incident1 min26 h
Never on its status page30
Status page delay (median)1 min1 min
30-day hazard rating4.7 / 108.3 / 10

MongoDB's worst incidents

MongoDB's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
MongoDB Critical Flaw Allows Database Servers to Crash via Two Ping Requestscriticalongoingnot yet
MongoDB Server CVE-2026-120822 and CVE-2026-120825 Authorization Vulnerabilities

Cause: Authorization checks for replication administrative commands relied on client-supplied values, and privilege evaluations during view definition validation failed to cover nested pipeline portions.

highongoingnot yet
MongoDB Server Schema Validation Race Condition Causes Unexpected Termination

Cause: A race condition occurs in the schema validation component when concurrent writes are checked against a collection validator utilizing geospatial query operators.

highongoingnot yet
MongoDB: Issue impacting Atlas Search availability on certain clusters

Cause: The issue was identified as an anomaly in the mongot service causing crashes.

high1 minfirst
MongoDB: Trigger processing may be delayed globallyhigh1 minfirst
Full MongoDB outage history

Supabase's worst incidents

Full Supabase outage history