Help for owners
My Supabase project got paused or my app gets limit errors
Short answer
Supabase can restrict a project that exceeds its plan quota: pausing it, making the database read-only, or returning HTTP 402 on API requests. A paused project can be restored from Supabase Studio within a documented window. Usage limits and the spend cap setting decide which applies to you.
Does this sound like your situation?
- The app suddenly cannot read or save anything.
- The dashboard shows the project as paused.
- Requests fail with a 402 error.
- Saving data fails but reading still works.
- I got an email about exceeding the quota.
Why does this happen?
The plan's quota was exceeded
On the Free plan you are notified when you exceed the quota, and if you keep exceeding it service restrictions apply. On the Pro plan with the spend cap on, restrictions can apply if you keep exceeding limits without managing usage or turning the cap off.
Confirmed by supabase.com
Restrictions come in several forms
Supabase lists pausing projects, switching databases to read-only, disabling new project launches or transfers, and returning HTTP 402 for API requests. Usage-based restrictions lift when the quota refills at the next billing cycle, or sooner by upgrading from Free or by turning the spend cap off on Pro.
Confirmed by supabase.com
An unpaid invoice
The same billing FAQ says projects can be restored once all outstanding invoices are paid, which means overdue invoices can lead to restrictions too.
Confirmed by supabase.com
A paused project has a restore window
Supabase documents a one-year window in which a paused project can be restored from within Supabase Studio. After that, the backup file and Storage objects can be downloaded from the dashboard and restored into a new project or locally.
Confirmed by supabase.com
The app was sending far more than expected
A loop in code, a missing cache or a bot hitting the API can use a month's quota quickly. That is a code and traffic question that the plan page cannot show.
What can I do about it today?
- Open the Supabase dashboardCheck whether the project says Paused, and read any banner or email from Supabase. Note the exact wording.
- Look at the usage pageSee which limit was passed: database size, bandwidth, storage or requests, and when.
- Restore only after you read what it doesRestoring is done from Studio in the documented window. Free projects also move to the latest minor Postgres version when restored, so tell your developer first.
- Do not delete the project or create a fresh one in a hurryA new project starts empty and your users and data stay in the old one.
- Download a backup if you canThe dashboard offers backup and storage downloads for a paused project. Keep a copy somewhere you control.
- Decide who owns the accountCheck that the Supabase organisation is in your company's name and billing email, not a former developer's.
When should I bring someone in?
- The app is down for customers and you cannot tell which limit was hit.
- The project is outside the restore window or the restore fails.
- Usage is far higher than your traffic explains.
How do I handle it?
- Read the project state and usageI check the dashboard for the project status, quota graphs and the restrictions in force.
- Take a backup before touching anythingA database dump and a copy of stored files are saved before restoring or changing the plan.
- Find what used the quotaI look at query volume, large tables, file storage and API traffic to see what grew.
- Fix the cause, then the planHeavy queries, missing caching and runaway jobs are fixed in the code, and the plan choice is laid out for you with the trade-offs.
- Set alerts and ownershipUsage alerts go to your email and the account is placed under your organisation.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is my data lost when a project is paused?
Supabase documents a one-year window to restore a paused project from Studio, and download options for the backup and storage after that.
Do I have to upgrade?
Not always. Quota restrictions lift at the next billing cycle, but upgrading or changing the spend cap lifts them sooner. Whether that is worth it is your decision.
What does a 402 mean?
Supabase lists HTTP 402 for API requests as one possible usage restriction. Check the billing and usage pages.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.