Production Database Down — Need Host Migration
My database is completely down. The SQL editor can’t run anything — getting read ECONNRESET. Auth, Realtime, and Storage are all unhealthy even after restarting the project and scaling up. I have been trying to fix this for a week and I’m honestly over it.
8 Replies
You restarted the entire instance or just the DB?
If you can't find anything in the logs, going to be hard for users here to help.
Have you verified the same dashboard issues from another browser or device?
You scaled up which means you are Pro did support not have anything for you?
I restarted the entire instance by changing compute from Micro → Small and back, which redeployed the whole container. The issue persists — System is still 11.71 GB even though my database size is basically 0 GB.
I’ve tested the Supabase dashboard on multiple browsers and devices, same results:
• Tables often don’t show up
• SQL editor sometimes drops with ECONNRESET
• Infrastructure page for Postgres upgrade also fails with ECONNRESET
I’ve already contacted Supabase Support but haven’t gotten a solution yet — they suggested a container rebuild or right-sizing the disk since it’s stuck at 12 GB due to System bloat.
Not sure what a container rebuild is in their hosted system.
You are waiting for a user who has hit something like this here for advice. Support seems the best avenue for this.
Perfect I guess I will just have to wait this is. Frustrating because I can’t build anything on my software until supabase is backed up and running any advice on preventing this from happening in the future do I just need to upgrade my plan and my disk size?
There is not info to know. Not clear from what you present what is actually causing it.
You would need errors from the Postgres logs or something definitive to act on like DB tables getting growing faster than you expect.
If you are saying your DB grew faster than the 8G to 12G to xG Disk upgrade in 6 hours (I think that is the max limit for upgrades) and that kept you from upgrading the disk then allocating large disk or figuring out why disk is so big is critical.
I don’t know if this helps are not any time I look at Postgres it says error as well.
I literally don’t know why it’s doing this. My supabase has always worked but once I added cron jobs and integrated my ai worker from digital ocean to pull tables from supabase it has not worked ever since.
Support I would think could tell you why it is in that state.
You seem to have your disk capped.
If you could run dashboard you could check the cron schema tables for size. If you have a cron tasks at a very high rate (< minute) then you have to make sure you also clean up the cron tables as called out in the cron extension repository.
Also how fast is digital ocean hitting your DB?
What was your disk size before the trouble started?
Out for the night.