PostgreSQL · error reference
Supabase: connection failed — Network is unreachable
connection to server at "db.abcdefghijklmnop.supabase.co" (2406:da14:…), port 5432 failed: Network is unreachable
The password is not the problem — it was never sent. Supabase's direct database host has only an IPv6 address, and the network you are connecting from only speaks IPv4.
What the database is telling you
db.<project-ref>.supabase.co resolves to an IPv6 address and has no IPv4 (A) record unless the project has the paid IPv4 add-on. A client on an IPv4-only network — many cloud servers, CI runners and offices — cannot route to it, so the connection fails before PostgreSQL sees it: "Network is unreachable", a timeout, or even "could not translate host name" depending on the client.
Why it shows up in a migration
Most hosted migration tools, CI systems and serverless platforms connect over IPv4. Credentials copied from Supabase's direct connection string fail from all of them, and the error looks like a network fault rather than a choice of host.
Common causes
- Using the direct connection host from a network without IPv6.
- A client that resolves the name but has no IPv6 route, and reports it as unreachable or a timeout.
How to fix it
- 1
Confirm it: the host has an AAAA record and no A record.
dig +short AAAA db.abcdefghijklmnop.supabase.co # an IPv6 address dig +short A db.abcdefghijklmnop.supabase.co # nothing
- 2
In Supabase, open Connect and use the Session pooler details — an IPv4 host, port 5432, and the user name with the project ref appended.
host: aws-0-<region>.pooler.supabase.com port: 5432 user: postgres.abcdefghijklmnop password: (the same database password)
- 3
The Transaction pooler (port 6543) also works over IPv4, but it shares server connections between transactions, so session state such as prepared statements does not carry over; for a tool or long-lived service, prefer the Session pooler.
- 4
Or enable Supabase's IPv4 add-on if the direct host must be used.
What DBShifts does about it
Connection diagnosis checks whether the host has only IPv6 addresses before it blames credentials. For a *.supabase.co host it says so and names the Session pooler fix — this came from a real failed connect, where the error had been sending the owner back to re-type a password that was never tried.
Connection diagnosis
Connecting a database?
Add the database to DBShifts and the connection is tested on the spot. If it fails, you get which of these errors it is and what to change — not the driver's raw message. Once it connects, browse it, migrate it, or let an AI agent read it through the gateway with sensitive columns masked.