garyaustin

Could be but sort of odd for this many so quick... BUT also in different regions... Your usage charts or Observability database reports should show a rise in usage.

There is also an audit log in account settings that shows org deletions. Check that also.

I don't know what that means. Even if downgraded orgs would not go away. Seems like you are in a different account somehow? Was the project created in Supabase or something like Vercel/Lovable/Bolt?

Did you try device/browser/vpn yet?

You said you were free. And we have no way to bump plans only flag thru an informal queue after 6 hours of no automated 2nd reply after first email.

They status you are showing is typical for overloading the server. So could be just coincidence. The thing that I do consider possible for outage is if finalrock44 has multiple instances in same state at same time. <@320845717335834624> make sure you file a support request.

Would be odd as everyone is running on different servers for the most part. <@297311965691248640> what region?

Did you log back in and are hitting issues or can't log back in? Try a different device/browser/vpn.

What is the project health on the home page? Look at usage in settings and database info in Observability. If you filed your ticket thru the dashboard then your upgrade should be associated with it. Disk I/O burst being depleted is the most common reason for this, but there are many. It slowly builds back up again over 24 hours unless you keep hitting the DB.

Not sure what you mean by deleted. When you restore a project that was paused less than 90 days you should get back your storage schema and storage files. I've not heard of that process not doing that. How have you determined it is deleted? Note no one here can help with your project directly though or see behind the scenes. That can only be done thru support.

Are the tables that are having stuff deleted in that security warning list? If so the those REST API deletes did not need "admin" keys and are likely the source of the issue. They are certainly not from Supabase. So either you or someone out to screw with you.

Sendgrid, Brevo, Resend are all good quality SMTP providers.

Here was another thread on exactly 200 seconds but don't see a final answer... https://github.com/orgs/supabase/discussions/36497

Just a note on 400 seconds that is only for background tasks. It is 150 seconds to finish the http call to the function.

I don't know how many use Microsoft SMTP so that could be why no other reports if it is some issue between them and SB versus something in your setup.

And do you see error in their logs? I would speculate something changed there and then either has an issue with what Supabase does or is a bug.

And a common SMTP provider or not? You say SMTP hosts so maybe that is what you mean. Also you might test real quick the default SMTP provider. I'm using Brevo with no issue.

I'm on the latest Auth version in my instance (from infra settings 2.189) and no issues sending password reset.

Are you using a common SMTP provider? Any logs there? No other reports so far.

You can only get help thru support for this.

The employee in our informal queue marked this as flagged to the correct team back on the 27th. Did you get any follow up emails? Check Spam?

You should contact support from top right of dashboard and stay project stuck restoring in title.

You get two free projects for account not specific org. If you have access to two free projects as a team admin that counts.

That would not be related to support but it does say you have tables that can be wiped out by anyone... So they would not need your private keys.

Right but you did not after I mentioned it on 5/4 before, so was just saying that without nothing we could do. I bumped yesterday as I said after I saw it from your post yesterday. The employee marked it as picked up. Did you get a follow up email? But it has been bumped by us now.

I added it to the INFORMAL queue ONE employee checks when he can to get it out of general support to infra. You will then be behind all Pro plans and Free before you once you get that message. You should never pause a project that is having issues as it has to do a backup up which will likely fail in order to switch to a new s3 instance when you Restore it. Restart is the thing to do.

Just realize though it is highly likely on your end for what is causing this.

I'm just seeing this. Without the ticket # we have no way to put it in our INFORMAL queue AN employee checks when he can to move it to the right team. I'll check if it was added after you posted it and add it if not. We will get no status updates on it.

It has not been added to our informal escalation path for "lost" tickets as you never responded about 2nd email and did not leave a ticket #. We don't have status here as this is a user helping user forum mainly. And can't estimate. How did your project get Paused as that is only for project not being used anymore?

I'll mention that but once it gets picked up should move faster than if Free.

There is none. It depends on when the employee that informally does this checks and then all he can do is make sure it gets out of general support to the right team. Where you Free or Pro?

I added it to the queue we have.

And where there any other emails after that?

You get the ticket # in minutes. Check your Spam.

Did you get a ticket # back? Any follow up email after that? Only support for this is thru that channel. You can drop your ticker # here and we have an informal way make sure not lost. This site is mainly user helping user.

Have you tried Lovable's Discord?

I don't know anything about Lovable internal process. You did not put that in your title so user/mods who might would not have been drawn to it. But in the end for sure Supabase team has no ability to access Lovable projects directly from end users. The projects are done thru some sort of white label deal that does not include SB enduser support.

You would have had to create the project in Supabase directly with their dashboard to get Supabase support at all. And to be clear as you said "your side" this is a user helping user forum and not monitored regularly by Supabase.

If this is lovable cloud then only they can work on the instances. Supabase does not have access and all support is done thru Lovable.

And no we have no way to escalate individual project issues around support. We can bump though ticket # 's after 6 hours or so without a follow up email. But have to have a ticket # from the first email. I assume you are Pro and our informal escalation path for project down issues is normally slower than for Pro support getting to the ticket.

Have you checked your Spam folder? You should fairly quickly have gotten back a ticket # email.

Try with another browser or device. Try with any anti-virus like bitdefender off.

If your project shows healthy and restart does not resolve it then probably have to wait for support. Did you get a follow up email about being moved to infra? Staff does not monitor here much.

It is against the rules to shout mods for non forum issues. No idea the context of what your AI is coming up with. You need to provide more info on what migrations and what error you are getting.

Broadcast with a database trigger to send is the best way over Postgres Changes. Only other way is to poll.

Maybe a CPU upgrade depending on reason.

If you are Pro then only way is Team plan. How long since ticket? Did you get a follow up email saying moved to correct team?

There is a restart in general settings. Otherwise support is only way to get help.

Not sure what this has to do with the OP's post. May need to post a new topic with more info. What is health of project from home page? Any usage warnings in particular for CPU/Disk I/O? Did you try restart?

You should check your usage reports and Observability Database charts and see if anything started spiking before the failure.