2 people reported

All time, since Jun 30.

Database unreachable after restart

“REST/Auth return Cloudflare 522; the pooler returns connection to database not available; Supabase's own mgmt-api gets 522 from the instance.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/supabase/issues/9709/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Database stays unreachable after resize or restart while reported healthy. REST and Auth return 522 and direct connections fail, while the dashboard or Management API shows Active/Healthy.

Is this your bug?

File my report
Where
hosted projects
Error text
connection to database not available
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Project inaccessible after restore9 people
  2. Project stuck Unhealthy with 521s2 people
  3. Disk-full WAL crash loop7 people

Original reports2, newest first

  1. Production Supabase down 12+ hours (us-east-2) and nobody responding: Postgres never restarts after resize, API says ACTIVE_HEALTHY#51135
  2. sa-east-1: project down 2 hours, restart failed (capacity), resize completed but still 522 on Auth/REST#47473

Do you work on Supabase?

Claim its RAP Sheet to see what your users report and answer them in one place.