Restore stuck >36h – Possible critical bug (project locked in "restoring" state)

[TheodoroNeto]

My project has been stuck in the "restoring" status for over 36 hours, now approaching 48 hours, without any visible progress.

Even though the status hasn’t changed, I can still perform some actions like SELECT, INSERT, DELETE queries, and some Edge Functions are working — but not all. RLS policies seem to be intact, and the database partially responds. However, several features that rely on the Supabase dashboard or API are still broken.

The Supabase dashboard itself is unresponsive — I can’t make any structural changes, and every action or navigation leads back to the “Restoring Progress” screen, making it impossible to use most of the platform’s core functions. It’s like being locked in a read-only state, with no clarity on what's actually happening.

Important note: this wasn't a manual process. I used the native restore option from within the Supabase dashboard, selecting a previous backup. Since then, the system has been stuck.

I’ve already reached out to support, but I haven’t received any reply — it’s been almost 2 full days.
This might be a critical or permissive bug, since the platform allows partial functionality while blocking essential updates.

Any help or guidance would be greatly appreciated.

Thanks.

[infotim3]

did you ever get any help or get it resolved?