Big delays since yesterday evening
Hello, since yesterday evening i'm noticing big delays when i use my NextJs app in Vercel. I was using the same queries for weeks but now the delays are very big. Sometimes it is ok, but most of the times it is very slow. I'm seeing some issues like "Transaction API error: Transaction not found. Transaction ID is invalid, refers to an old closed transaction Prisma doesn't have information about anymore, or was obtained before disconnecting." or "Transaction API error: Unable to start a transaction in the given time."
My code didn't change. Is there an issue in general?
54 Replies
Yes there is
Experiencing same issues
Same errors
any updates on this?
Status page shows all green and so far no response on urgent supabase support requests.
Seems they are completely unaware of the issues so far.
the status page not updated is not a new thing
it's the second time we have an issue with them, and the status page is not indicating any issues
For how long are you having the issues?
For us roughly since yesterday 12 UTC.
But much worse today
You are all getting transaction API error?
The OP is using Prisma Are you all using Prisma?
What regions?
yes, we are using prisma, and the same error
Migrations: aws-0-eu-central-1.pooler.supabase.com:5432
Are you using Supavisor pooling port?
Queries: aws-0-eu-central-1.pooler.supabase.com:6543/postgres?pgbouncer=true
we use pooling for database queries, but direct url for migrations and build time
What region and Supavisor port?
If any of you are Pro you should to with pg_bouncer.
Central Eu - region
K. And you all have support requests in?
I'll bump it as there are 3 of you.
supabase.com:6543/postgres?pgbouncer=true&connection_limit=60
yes, i did just made a support ticket
@garyaustin Thanks for bumping this.
Using pg_bouncer and getting these issues:
- Transaction API error...
- Timed out fetching new connection from connection pool...
- Unable to start transaction...
And generally getting AVG response times of 60s that were previously <1s for weeks.
When I say use PG bouncer I mean if you are Pro pay for the IPv4 if you need it and use the dedicated PGbouncer port (not the flag prisma needs) you get as it gets you have the shared Supavisor pooler.
so, do we have to change someting or not?
i dont really understand what's supposed to be the problem
My GUESS is there is a Supavisor issue limited to Central EU.
We are on Pro. Only using IPV4 for migrations. Might try for queries as well now.
Nothing you can do to fix a Supvisor outage if that is it.
BUT if Pro Supabase recommends you use the direct Port 5432 and the PGbouncer installed with your instance now instead of Supavisor if you can.
so, do you work on that issue related to Supavisor?
im gonna try with direct connection on 5432
There are no employees here if that is what you mean by do I...
This is a user helping user forum.
but you are in the support team, right?
NO
Seemss to be more than just Central EU: https://github.com/orgs/supabase/discussions/38519
There are in general no employees here.
Some of us are comped by Supabase to help out.
I have no direct access to Supabase except thru a shared slack channel.
a ok, sorry, I saw your message related to the suport tickets
I'm asking that you have support tickets in. That is the only way they might know if not a "MASS" outage with others reporting to them.
I'll add that discussion thanks. Just got up and had not looked thru Github yet.
Hi, I'm from the pooler team, would you please share the ticket id? I can then look closer
Hello, here is @paaulfff ticket number SU-243541
SU-243527
We have been having this issue since this morning, for the past 8-9 hours, some requests even take 4-5 minutes to complete
Thank you, Investigating
For us issues started at ~2pm yesterday and TTFB going from <1s to ~40s yesterday, to >1min today.
Just to give an update, I identified a potential problem, will be trying a fix
Awesome, let us know !
Could you please take a look in your side to see if its faster for you?
It's still slow and I get error 500 on some requests
it's a gamble, let's say I have 4 requests, it's either 3 are working, or just 2 are working, I just have to keep refreshsing until the stars decide to align and have all the queries working at once
now i had instant loading of the data, but if i refresh again or do another request it takes a lot of time
there is a new user on github with the exact same issue I have
error
:
"\nInvalid
prisma.client.findUnique() invocation:\n\n\nTimed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)"
Now it is a bit faster, but some requests keep having a 500 statusYeah. I see some improvement in your metrics but its still not good.
These are some of the types of errors we are seeing.
Same, we have several hundreds errors like that one
Everything looks good on our end at the moment. There have been no errors or timeouts for the last few minutes.
We do not use prisma, we connect to supabase via node-postgres.
I'm restarting one instance now. You may see some impact (different errors?) but after that is finished, I believe timings should get better.
Okay, let us know when it's done, we are still having random completion times.
We will be opening an incident for this
Thank you, looking forward to your update
It was improved some minutes ago but i'm still getting errors like |Can't reach database server at
aws-0-eu-central-1.pooler.supabase.com:6543|Hello, we had the same issue. There were many timeout errors (> 15s) with Next.js serverless functions that query from Postgres at Supabase. The system is hosted at Vercel, we use Prisma, and the region is eu-central-1. We use the shared pgBouncer (port 6543).
I could not see the error in the past hour.
I'm at under 6-7 seconds now compared to this morning where the app was not usable, maybe it will get improved once all is fixed.
It all looks stable for us for a while now.
Can confirm. Thank you @Void @garyaustin
Looks good on my side too, thanks guys ! Hope everything will be fine tomorrow 😄
Have a nice day/evening !