aws-1-us-east-2 shared pooler timing out
- We run a Spring Boot service on Fly.io (region sea) using Supabase’s FREE plan shared Supavisor pooler (db.ProjectID.supabase.co, project region aws-1-us-east-2).
- Starting ~2025-10-22 03:05 UTC our Fly machine can’t complete a TCP handshake to port 5432 on that host. nc -vz db.cdkgg... 5432 from the machine hangs and throws connect
to ... port 5432 (tcp) failed: Connection timed out, and traceroute6 stops right after Fly’s first hop.
- Nothing changed app-side; secrets are correct. Our beta project (different Supabase host, same Fly region) still connects instantly, so the issue seems isolated to this prod
project’s IPv6 route/Supavisor instance.
- We’re on the free tier so only Supavisor is available (no dedicated pooler / IPv4 add-on). Is there a known incident with the aws-1-us-east-2 Supavisor nodes, or can someone
from Supabase confirm whether this host needs a reset?
- Happy to DM project ref if needed; just want to know if others are seeing it or if there’s a workaround beyond waiting.
- Starting ~2025-10-22 03:05 UTC our Fly machine can’t complete a TCP handshake to port 5432 on that host. nc -vz db.cdkgg... 5432 from the machine hangs and throws connect
to ... port 5432 (tcp) failed: Connection timed out, and traceroute6 stops right after Fly’s first hop.
- Nothing changed app-side; secrets are correct. Our beta project (different Supabase host, same Fly region) still connects instantly, so the issue seems isolated to this prod
project’s IPv6 route/Supavisor instance.
- We’re on the free tier so only Supavisor is available (no dedicated pooler / IPv4 add-on). Is there a known incident with the aws-1-us-east-2 Supavisor nodes, or can someone
from Supabase confirm whether this host needs a reset?
- Happy to DM project ref if needed; just want to know if others are seeing it or if there’s a workaround beyond waiting.
