Urgent: Production Database Tables Dropped - Need Help Recovering Data
🔢DB Connections
Hello Supabase Team,
I urgently need help recovering my production database. All tables were accidentally dropped
from my database today (March 22, 2026) around 11:00-11:30 AM due to running prisma db push
--accept-data-loss during a deployment.
Database Details:
- Project Host: aws-1-ap-southeast-2.pooler.supabase.com
- Database: postgres
- Schema: public
- Plan: Free Tier
What Happened:
- Production database had multiple tables (shops, users, products, categories, items,
whatsapp_setup_requests, etc.) with active customer data
- During a backend deployment to Railway, Prisma ran db push --accept-data-loss which dropped
and recreated tables
- All production data is now lost
- Only the _prisma_migrations table remains
Current State:
- Running this query shows only one table exists:
SELECT table_name FROM information_schema.tables WHERE table_schema = 'public';
-- Result: Only _prisma_migrations
- Last migration in _prisma_migrations is from Feb 27, 2026 (changing shop_id to UUID)
- Database was working perfectly until this morning
What I Need:
1. Is there any way to restore the database to a state from this morning (before ~11:00 AM March
22, 2026)?
2. Do you keep any internal backups or transaction logs that could help recover the data?
3. Any point-in-time recovery options available, even for free tier in emergency situations?
Impact:
- Multiple shop owners cannot access their catalogs
- All customer/product data appears lost
- Business operations are completely stopped
I understand free tier doesn't include automatic backups, but I'm hoping there might be some way
to recover from your internal systems. This is a critical production issue affecting multiple
businesses.
Any help would be greatly appreciated. Thank you!
Supabase project ID: puvtxehzupqrnjfekooc
email associated with the Supabase account: durgeshsingh11111@gmail.com
I urgently need help recovering my production database. All tables were accidentally dropped
from my database today (March 22, 2026) around 11:00-11:30 AM due to running prisma db push
--accept-data-loss during a deployment.
Database Details:
- Project Host: aws-1-ap-southeast-2.pooler.supabase.com
- Database: postgres
- Schema: public
- Plan: Free Tier
What Happened:
- Production database had multiple tables (shops, users, products, categories, items,
whatsapp_setup_requests, etc.) with active customer data
- During a backend deployment to Railway, Prisma ran db push --accept-data-loss which dropped
and recreated tables
- All production data is now lost
- Only the _prisma_migrations table remains
Current State:
- Running this query shows only one table exists:
SELECT table_name FROM information_schema.tables WHERE table_schema = 'public';
-- Result: Only _prisma_migrations
- Last migration in _prisma_migrations is from Feb 27, 2026 (changing shop_id to UUID)
- Database was working perfectly until this morning
What I Need:
1. Is there any way to restore the database to a state from this morning (before ~11:00 AM March
22, 2026)?
2. Do you keep any internal backups or transaction logs that could help recover the data?
3. Any point-in-time recovery options available, even for free tier in emergency situations?
Impact:
- Multiple shop owners cannot access their catalogs
- All customer/product data appears lost
- Business operations are completely stopped
I understand free tier doesn't include automatic backups, but I'm hoping there might be some way
to recover from your internal systems. This is a critical production issue affecting multiple
businesses.
Any help would be greatly appreciated. Thank you!
Supabase project ID: puvtxehzupqrnjfekooc
email associated with the Supabase account: durgeshsingh11111@gmail.com
