supabase db push fails with timeout/unexpected EOF when connecting to pooler (crash id 4541e7a16532408182bccc315fba5d59)

[aissantos]

Title: supabase db push fails with timeout/unexpected EOF when connecting to pooler (crash id 4541e7a1...)

Summary

Running npx supabase db push -p '<password>' against the linked project bpivdezffjeyzukfzhcl fails intermittently: authentication completes (SCRAM-SHA-256) but the connection is interrupted (timeout / unexpected EOF) and the CLI exits with a crash report.

Environment

• Supabase CLI: v1.226.4
• Project ref: bpivdezffjeyzukfzhcl (project name: finansix_core)
• Pooler host: aws-1-us-east-2.pooler.supabase.com
• Local env: Ubuntu 24.04 devcontainer
• Command: npx supabase db push -p '<password>' (also tried with --dry-run and --debug)

Steps to reproduce

1. Authenticate with npx supabase login and link the project (npx supabase link --project-ref bpivdezffjeyzukfzhcl).
2. Run npx supabase db push -p '<password>' --debug.
3. Observe repeated successful SCRAM authentication messages followed by failed to receive message (timeout: context deadline exceeded) or failed to receive message (unexpected EOF) and finally a crash report.

Observed behavior (excerpt)

• Debug shows SASL authentication flow completing with AuthenticationOK.
• Shortly after, the connection attempts to different backend IPs succeed in the handshake but then fail with EOF/timeouts.
• Example errors seen: failed to receive message (unexpected EOF), timeout: context deadline exceeded.
• CLI produced a crash report with ID: 4541e7a16532408182bccc315fba5d59.

Debug excerpt

2026/01/06 17:06:03 PG Recv: {"Type":"AuthenticationOK"}
... repeated auth OK across different backend IPs ...
failed to connect to postgres: failed to connect to `host=aws-1-us-east-2.pooler.supabase.com user=postgres.bpivdezffjeyzukfzhcl database=postgres`: failed to receive message (timeout: context deadline exceeded)
Sent crash report: 4541e7a16532408182bccc315fba5d59

Additional context

• I was able to apply migrations successfully to a local Supabase instance (npx supabase db push --local --include-all).
• A previous attempt to push to remote failed earlier with permission denied for schema auth when applying 20240105000002_rls_policies.sql (creating functions in auth schema). That aside, the current blocking issue is intermittent pooler instability preventing any push from completing.

Request

Please investigate pooler connectivity/timeouts for project bpivdezffjeyzukfzhcl. The CLI can authenticate but the connection is interrupted afterward; logs and crash ID are included above. If you need further logs or a trace, I can re-run with --debug and attach full output.