[CRITICAL OUTAGE] Need pre-pause snapshot restoration - Pro Plan (Project: otbpqhbpkzdzszmydedn)

[cenitscore-ctrl]

Hello Supabase Team & Community,

We are experiencing a critical production outage and urgent database issue on our Pro Plan project.

Issue Details:

• Project Reference: otbpqhbpkzdzszmydedn
• Organization: cenitscore-ctrl's Org
• Plan: Pro Plan
• Affected Account Email: cenitscore@gmail.com
• Support Ticket: Already submitted via Dashboard (Severity: High/Urgent)

Summary:

Our project was previously paused. After upgrading to Pro and unpausing/restoring the database, the core production tables (such as clubes, players, visits) are empty.

We urgently need an engineer from the Database Reliability / Support team to assist in restoring the pre-pause physical snapshot or cold volume backup taken around October 11–12, 2026.

We give full authorization to restore/overwrite the current empty instance with the pre-pause physical volume snapshot.

Our app is currently down in production. Could someone please help escalate or look into our open support ticket?

Thank you very much!

[shahsuraaj-hub]

While the ticket is open, two checks take a minute each and change what support needs to do.

1. Count the rows as the database owner. The SQL Editor runs as postgres, so RLS can't hide anything there:

select 'clubes' as table_name, count(*) from public.clubes
union all select 'players', count(*) from public.players
union all select 'visits', count(*) from public.visits;

If the counts are above zero, the data survived and the app is being blocked, usually by RLS policies or missing grants. That's fixable today, with no restore.

2. Check that the app points at this project. The ref inside its SUPABASE_URL should be otbpqhbpkzdzszmydedn.

If both check out and the counts are zero, open Database, then Migrations, and look for anything applied after the restore: a migration or seed that recreates those tables on reconnect empties them. Until support replies, don't run migrations or seeds, and add the counts and your exact pause and restore times to the ticket. What do the counts show?