39 Replies
Yeah this is causing grey-outs on our site as well. Any updates?
Started a support request but nothing back yet
Same. We’ve DMed the team but nothing yet.
So are you two are it here and github.
Working for me in us-east
Hm?
Not sure what DM'd the team means.
You need to make a support request.
Not sure what it means either; someone else on my team (Nick) reached out
@garyaustin do you have any info you can provide us?
No. You two are it so far. I've tested 3 of my instances and they work fine.
What is your symptom?
Extremely high latency in our API
Do you have a support request in?
same
We use the supabase client from lambdas deployed with SST
and yes we have a support request in
What region are you both in?
Us-east-q
1*
us-east-1
Extreme latency observed for us-east-1 as well
Our ticket ID is SU-237145
ours is SU-237155
same
Showing tickets here does no good.
We observe no abnormal statuses on AWS service health dashboard for the same region
This site is not monitored by Supabase regularly.
@knexguy what is your region?
Us-east-1, also experiencing a high latency from REST calls
Other regions appear to have nominal latencies. Us-east-1 appears to have jumped from ~80ms to ~2.7kms
My us-east-1 is working, but can't really judge latency.
Don't know if it has todo with my issue, but I'm trying to upload a file with 87MB size and it get stucks at 25%, after 2 minutes I have to login again because spabase sais JWT expired.
Probably not. Are you in us-east-1?
I've bumped it to my contact path based on 3 of you in a short period of time and the odd status page.
Maybe CF related? I don’t know anyone else to returns 520s
this is happening for our company as well. degraded latency of all supabase endpoints causing timeouts
us-east1? You have a support request in?
yes, us-east1. and not yet - was just researching if others ran into this issue too
Please do. They have not noticed my slack message yet... but could already be working it.
I filed an email support request!
No need to put your instance id here.
I’m 75% confident this is caused by a network issue in Cloudflare. They have an open incident report for IAD
Would not be the first time.
IKR, thanks Google…