xxxx.supabase.co | 525: SSL handshake failed
Seeing a ton of 52X errors and SSL handshake failed but no downtime reported.
56 Replies
Same here
I know the status board is commonly not in real time so something is probably down...
for me postgres and auth unhealthy
Yeah something is off
ditto, this is like the second time in a couple months I've had a production outage
truly thinking of migrating off which will be a massive pain
same here
+
lots of errors and timeouts hitting the DB
restarting the server doesn't resolve the issue as well
Everything is fine now.
right yea
its suddenly back
i hope this isn't a common issue lol
Nope
It's like the second this year
(The first one was not their fault but Cloudflares)
And it's gone again 🙂
yep everything broke again
Bunch of people on twitter too
Omg, I think I'll stop using Supabase for prod projects
This channel is not for your future plans blud
does supabase have any on-call engineers?
i hope someone is looking into it lol else the extended downtime would be a bit of a pain
I don't even see staff being online right now
guess we might need to wait till someone wakes up
Someone in a diff thread noted a full restart worked for them: https://discord.com/channels/839993398554656828/1410540764525625374
Didn't help for me
Same for me
This just costed me a client. Where can I check whats wrong?
well not the status page lol https://status.supabase.com/
Supabase Status
Welcome to Supabase's home for real-time and historical data on system performance.
@garyaustin
Not the first time when they didn't show anything but hours later
yeah thats the usual
same here
Do you guys using Cloudflare or not?
https://www.cloudflarestatus.com/
Apparently cloudfare could be cause
Cloudflare Status
Welcome to Cloudflare's home for real-time and historical data on system performance.
But my supabase is in us-east-1 region
where are yalls servers located?
same
same
I'm having issues with my site too. us-east-1.
also us-east-1
also us-east-1
Did restart didnt fix, did pause and restore, that worked took few minutes, or they fixed the issue dont know
is supabase down, getting cross errors suddenly
I took this downtime opportunity to do a project upgrade to the latest version of Supabase, and now mine is working again.
randomly it is now back
looks like it's back
its back for me too
back for me too
for me too 🙂
i want an hour of sleep back
back for me too.
for us it failed from approx 11:40am to 12:30pm (utc+2). Actually maybe a bit less than 50min. That's quite bad imho
Was it your dashboard not working or your projects you are creating too using the Supabase API?
This is my fastapi server that uses the python sdk to connect to supabase https://github.com/supabase/supabase-py
It's still not clear to me if you are saying your project stopped working or the dashboard as you've linked to the
supabase-py project.it was the supabase subdomain lead request itself. dashboard was responsive still fine.
So auth requests, some client requests
The supabase dashboard seemed to work normally for me during that time (but I didn't use it much).
I think direct database connections (e.g. using a connection string with sqlalchemy) were still working (didn't try it a lot) but via the python sdk linked above did not work
Also found that my direct connections to the postgres string were working
Generally when you get CORS error in a situation like this it means there might be something wrong with Cloudflare, so I normally check their status page.
right, I checked their end and it was just some EU buckets
my db took a nose dive, my whole web app went down
