Fix

Supabase paused your project. Get the data out first.

Free-plan projects pause after about a week without activity. The data isn't gone — but the right response is to restore it, export immediately, and only then decide what's next.

Step 1 — restore from the dashboard

Open the project in the Supabase dashboard and click Restore project. Unpausing usually takes a few minutes. Don't postpone this: a paused project's data is retained, but retention policies change and a project you can't unpause is a support ticket, not a download button. Do it while it's routine.

Step 2 — export before anything else

The moment it's back, take a full dump through the Session Pooler (IPv4 — why the direct host may not work for you):

pg_dump -Fc -f rescue-$(date +%F).dump \
  "postgresql://postgres.<REF>:<PWD>@aws-0-<REGION>.pooler.supabase.com:5432/postgres"

That single file contains your tables, data, RLS policies and auth users. Storage files (uploads) are separate — pull them via the Storage API if you have any.

Step 3 — stop the cycle

• If the project matters, the honest fix is the Pro plan — pausing goes away.
• If it's a side project you want to keep on Free, any scheduled external backup keeps a copy safe no matter what the pause policy does. Full routine: backing up a Free-plan project.
• Pinging the project weekly to dodge the pause is fragile — it protects uptime, not data.

Related fixes: How to back up a Supabase Free-plan project How to actually test a Postgres backup