Paid $25 because diskIO maxed

I paid $25 to super Bass yesterday two days ago because my disc size maxed out. They I also changed from a nano or micro to a small and I still at no point in the last 3 days if I ever been given any resources or been able to hit an API.

I've been doing troubleshooting the best that I can but like I looked at it with Jim and I looked at with Claude and both of them are sending me that the issue was with supabase not substantiating my paid account.

Has anyone encountered a bug like this I've sent them four or five emails but I haven't heard anything back.

garyaustin•9/11/25, 9:28 PM

Did you at least get emails with ticket # back from them?
If you go into the dashboard do you see your ORG the project is in is not Pro?

Spicy YeetOP•9/11/25, 9:34 PM

It's showing is pro I have the tickets in my email yeah I've got like four or five of them.

garyaustin•9/11/25, 9:35 PM

So what do you mean you have not been given resource or able to hit API?

Spicy YeetOP•9/11/25, 9:36 PM

SU-245273 SU-245272. SU-245267

garyaustin•9/11/25, 9:37 PM

If you go to https://supabase.com/dashboard/project/_ what is your status. This is from the main project page.

garyaustin•9/11/25, 9:37 PM

Putting ticket numbers does nothing here. This is user helping user mainly.

Spicy YeetOP•9/11/25, 9:38 PM

It shows on my like homepage like on integrations that I've used .57 out of 8 GB of disk space. And then when I run an API whether it's from my local from Figma from my website, it tells me that I'm out of disk I O

garyaustin•9/11/25, 9:38 PM

Disk I/O is from how much you are hitting the disk with requests, not the size of the disk.

garyaustin•9/11/25, 9:40 PM

What is this section from here: https://supabase.com/dashboard/project/_/settings/infrastructure

Spicy YeetOP•9/11/25, 9:42 PM

Yeah I went here and I upgraded from nano to micro and then micro to small and then small to medium.

It's still the same issue I've agreed to give them like $100 a month.

Spicy YeetOP•9/11/25, 9:43 PM

It shut off my database and then it started it back up.

Spicy YeetOP•9/11/25, 9:43 PM

But I still can't hit it with an API

garyaustin•9/11/25, 9:43 PM

Can you show the Disk/IO image page section please.

garyaustin•9/11/25, 9:43 PM

What is the exact error you are getting?
Is it from the dashboard logs or from your client side?

Spicy YeetOP•9/11/25, 9:44 PM

"URGENT: REST API 503 errors persist after compute upgrade - Project

Spicy YeetOP•9/11/25, 9:44 PM

I cannot I'm actually walking into work unfortunately though I appreciate the help if you're around in a few hours I'll be back.

garyaustin•9/11/25, 9:45 PM

Yeah, I should be here off and on.
Need to know more about that error and where you are getting it.
Seems more like an AI message than an actual supabase error text.

garyaustin•9/11/25, 9:46 PM

If it is your instance though then you are stuck waiting for support.
BUT upgrading means you moved hardware and restart should clear out any locked up code.

Spicy YeetOP•9/11/25, 9:48 PM

Yeah I have upgraded it three times. I will post in here when I get back. Yeah I would give them money to have my data if they would accept my money.

Spicy YeetOP•9/12/25, 1:33 AM

I don't know where to find the image you polsted

Spicy YeetOP•9/12/25, 1:37 AM

garyaustin•9/12/25, 1:39 AM

The disk I/O one is right below what you just posted.
The project status should be at the link I gave which will ask for your instance to get the the page. But it is the main home page of your project.

garyaustin•9/12/25, 1:40 AM

You are definitely upgraded as you have 2G of memory

Spicy YeetOP•9/12/25, 1:53 AM

Weird, I can hit through postgres with passwortd,

Spicy YeetOP•9/12/25, 1:56 AM

I dont know man. This worked fine until they l,imited me now nothing works

garyaustin•9/12/25, 2:01 AM

I have no idea what you are trying do there.
You have not shown the other two status images I mentioned nor shown the exact 503 detail error message and where you are getting it.

The select you show above will not work as those column names don't exist pg_stat_user_tables. Why are you doing this query?

Spicy YeetOP•9/12/25, 2:01 AM

The Supabase API test returned a 503 error indicating the database is experiencing issues with schema cache retrieval. The API is returning a retry message, which suggests this might be a temporary service issue on
Supabase's end.

The status code 503 means "Service Unavailable" and the specific error PGRST002 with message "Could not query the database for the schema cache. Retrying" indicates that Supabase's PostgREST layer is having trouble
accessing the underlying database schema information.

This could be due to:

Temporary connectivity issues between Supabase and their PostgreSQL instance
Database maintenance or high load
Schema cache invalidation process in progressThe test successfully made the API call with proper authentication (no 401/403 errors), so the credentials and endpoint are correct.

garyaustin•9/12/25, 2:02 AM

Is that some sort of AI response?

Spicy YeetOP•9/12/25, 2:04 AM

Its the response to hit my table using anon

import requests

url = "https://gjfxvbudzyvvxmhlopke.supabase.co/rest/v1/espn_api_futures?limit=1"
headers = {
"apikey": "correct token",
"Authorization": "Bearer correct token"
}

response = requests.get(url, headers=headers)
print(f"Status: {response.status_code}")
print(f"Response: {response.text}")

Spicy YeetOP•9/12/25, 2:04 AM

garyaustin•9/12/25, 2:04 AM

Please show the status page.
And before you were saying Disk I/O issues.

Spicy YeetOP•9/12/25, 2:06 AM

Where is status? Idk what the issue is now

garyaustin•9/12/25, 2:06 AM

I showed you the image of the home page and the status info for your instance. It is off to the right.

garyaustin•9/12/25, 2:06 AM

I also gave you a link to that page.

garyaustin•9/12/25, 2:07 AM

Need to see if PostgREST is running.

garyaustin•9/12/25, 2:07 AM

Paid $25 because diskIO maxed

Spicy YeetOP•9/12/25, 2:07 AM

garyaustin•9/12/25, 2:08 AM

So instance seems to be ok.

Check the logs tab and go to PostgREST log and see if there is any meaningful error.

Spicy YeetOP•9/12/25, 2:08 AM

i see this:

garyaustin•9/12/25, 2:09 AM

Those are your RLS policies. Has nothing to do with this issue.

garyaustin•9/12/25, 2:10 AM

Spicy YeetOP•9/12/25, 2:11 AM

Gotcha, postgres logs: "Failed to load the schema cache using db-schemas=public,graphql_public,ffl,odds_api_silver,live_odds_api,exercise,live_nfl_py,live_nfl_ref,live_espn,live_pff and db-extra-search-path=public,extensions. {"code":"3F000","details":null,"hint":null,"message":"schema \"ffl\" does not exist"}"

Spicy YeetOP•9/12/25, 2:11 AM

garyaustin•9/12/25, 2:12 AM

Does it exist?

garyaustin•9/12/25, 2:12 AM

Schema ffl

Spicy YeetOP•9/12/25, 2:12 AM

idk where to find that setting

Spicy YeetOP•9/12/25, 2:12 AM

probably not

garyaustin•9/12/25, 2:13 AM

garyaustin•9/12/25, 2:14 AM

If it does not exist then go to here and remove it:

Spicy YeetOP•9/12/25, 2:16 AM

Found, yeah that was the problem. Dope, I would not have found that ever. Testing in website now

Paid $25 because diskIO maxed

Similar Threads

Similar Threads

Similar Threads