Supavisor Incident Ongoing
🔢DB Connections
Hey team — we’ve been experiencing serious issues connecting to our Supabase Postgres instance since November 28th, and our engineers have been debugging non-stop on our side.
After extensive testing and ruling out multiple hypotheses (including our own Vercel setup, serverless cold starts, and API-level timeouts), we’ve isolated the problem to Postgres connection hangs this morning. Specifically, our serverless functions consistently freeze on the first attempt to make a database query, with no logs past the initial DB call.
We saw the incident reported today involving Supavisor connection issues, which lines up exactly with the behavior we’ve been seeing. I was initially relieved to having found the explanation. However, even though the incident was marked as resolved around 12:30pm EST, we are still experiencing the same connection hang issues.
Is it possible to escalate this to someone to take another look at the issue? We are still seeing intermittent timeouts.
After extensive testing and ruling out multiple hypotheses (including our own Vercel setup, serverless cold starts, and API-level timeouts), we’ve isolated the problem to Postgres connection hangs this morning. Specifically, our serverless functions consistently freeze on the first attempt to make a database query, with no logs past the initial DB call.
We saw the incident reported today involving Supavisor connection issues, which lines up exactly with the behavior we’ve been seeing. I was initially relieved to having found the explanation. However, even though the incident was marked as resolved around 12:30pm EST, we are still experiencing the same connection hang issues.
Is it possible to escalate this to someone to take another look at the issue? We are still seeing intermittent timeouts.
