DEV Community

DebugRadar
DebugRadar

Posted on Originally published at debugradar.com

Fix: Supabase Database Connection Error

Originally published on DebugRadar.

Quick Fix Summary

  • Problem: On November 12, 2026, Supabase reported "Database Connection Errors" — increased connection errors, with some databases unavailable and all services unhealthy. A companion incident the same evening showed elevated error rates for all Supabase project APIs.
  • Fix: None user-side. Supabase resolved both incidents on November 12. Check status.supabase.com first, confirm your own project in the dashboard, and retry API calls with exponential backoff — do not redeploy, migrate, or rebuild in a panic.
  • What happened: Database connection errors: investigating 20:35 UTC → identified 22:38 UTC → monitoring 23:03 UTC → resolved 23:40 UTC (about 3 hours 5 minutes). API error rates: started 22:13 UTC → resolved about 23:30 UTC (about 1 hour 17 minutes). All 200 components operational since.

Technical Root Cause

Error Code Affected Version Root Cause Current Status
"Database Connection Errors" — increased connection errors; some databases unavailable with all services unhealthy. Companion: "Elevated Error rates for All Supabase project APIs" (Data APIs, Auth, Storage, other HTTP API routes) Supabase — a subset of projects across all regions (database incident); all regions' API routes (API incident) Not published for the database incident. For the API incident, Supabase isolated the error rates to a single project with a very unusually high request rate and determined there was no widespread issue Resolved Nov 12, 2026 — database incident 23:40 UTC (about 3 hours 5 minutes); API incident about 23:30 UTC (about 1 hour 17 minutes)

Step-by-Step: What to Do When Supabase Shows Database Connection Errors

Step 1 — Check Supabase's Status Page First

Open https://status.supabase.com and look for a database or API incident. On November 12 the page showed "Database Connection Errors" and, the same evening, elevated error rates for all project APIs. If an incident is open, the failure is Supabase's side — your project code and your database schema are not the problem. This is the same first move as our Fix: SQL Server Connections Stay Open After Update — when the vendor's own status page shows an incident, stop troubleshooting your own setup.

Step 2 — Confirm Whether Your Own Project Is Affected

Only a subset of projects were hit by the database incident. Check your own project in the Supabase dashboard before assuming it is down — if your project is green while the status page shows an incident, your errors are a different problem. Do not redeploy, migrate, or rebuild your project in a panic; the failure was server-side.

Step 3 — Retry API Calls With Exponential Backoff

For the API errors, retry with exponential backoff — a short wait, then a longer one — instead of hammering the API. The API incident lasted about 1 hour 17 minutes; steady retries ride it out, while a retry storm makes the error rates worse for everyone. The same discipline applied to the Cloudflare Workers API outage we covered in Fix: Cloudflare Workers API 5xx Errors — one retry after resolution, then investigate.

Step 4 — Read the API Incident Honestly

Supabase traced the elevated API error rates to a single project with a very unusually high request rate — not a platform-wide bug. If your API calls failed during that window, the cause was a noisy neighbour, not your code. Do not rewrite your integration over it.

Step 5 — After Resolution, Verify Before Moving On

Once the status page shows all components operational, run one clean check of your database connection and your key API routes. If they work, you are done. If a specific route still fails after resolution, that is a new problem — check your project logs before redeploying anything.

FAQ

Is my Supabase data safe?

The incident caused connection errors and unavailable databases — it did not report data loss. If your project was in the affected subset, check the Supabase dashboard for its current status before doing anything.

Should I redeploy or migrate my project?

No. The failure was server-side, and redeploying or migrating during an incident only adds risk. Check status.supabase.com, confirm your project in the dashboard, and retry with backoff.

What caused the API errors?

Supabase traced the elevated API error rates to a single project with a very unusually high request rate — not a platform-wide bug. The database connection errors were a separate incident the same evening, with no cause published.

Sources: Supabase status page (status.supabase.com), November 12, 2026; StatusPal Supabase incident timeline, November 12, 2026 (https://www.statuspal.io/status/supabase); Pingoru Supabase status report, November 12, 2026 (https://pingoru.io/providers/supabase).


Read the full guide on DebugRadar: Fix: Supabase Database Connection Error

Top comments (0)