Hi everyone, I need urgent help with a production issue.
storageauthMy Supabase project suddenly stopped allowing new user signups.
All attempts to create a user (both through my app and through the Supabase Dashboard → “Add User”) fail with:
• 504 Timeout – context deadline exceeded
• database error on committing or rolling back transaction: conn closed
The user is never created in auth.users.
Additional symptoms:
• Deleting rows from certain tables (assistants, page_views, profiles) also results in timeouts.
• Smaller deletes (like leads) work fine.
• Increasing compute from NANO to MICRO did not change anything.
• Storage shows only 0.48 GB used out of 12 GB.
• Cursor’s analysis suggests temporary Postgres storage or WAL may be saturated (~1.6 TB accumulated), which could explain the failing transactions.
This affects production and I cannot onboard new users at all.
Is it possible that the Postgres instance needs a restart or cleanup of temp/WAL storage?
Project ID: stobyer…
Any help or guidance would be extremely appreciated.
All attempts to create a user (both through my app and through the Supabase Dashboard → “Add User”) fail with:
• 504 Timeout – context deadline exceeded
• database error on committing or rolling back transaction: conn closed
The user is never created in auth.users.
Additional symptoms:
• Deleting rows from certain tables (assistants, page_views, profiles) also results in timeouts.
• Smaller deletes (like leads) work fine.
• Increasing compute from NANO to MICRO did not change anything.
• Storage shows only 0.48 GB used out of 12 GB.
• Cursor’s analysis suggests temporary Postgres storage or WAL may be saturated (~1.6 TB accumulated), which could explain the failing transactions.
This affects production and I cannot onboard new users at all.
Is it possible that the Postgres instance needs a restart or cleanup of temp/WAL storage?
Project ID: stobyer…
Any help or guidance would be extremely appreciated.
