Try or ByeTry or Bye

Supabase Database Connection 'Network Is Unreachable'

Workaround available Server, CI, local tools Updated October 21, 2026

Quick answer

The direct host db.<ref>.supabase.co is IPv6-only. Use the Session or Transaction pooler connection string (IPv4) from the Connect dialog, or buy the IPv4 add-on.

Most likely fix: Switch to the pooler connection string.

Symptoms

Connecting from Railway, Render, Docker, CI or a home network fails with 'Network is unreachable', 'could not translate host name' or 'Address family not supported'.

Why it happens

  • Direct connection resolves only to IPv6
  • Hosting provider or network lacks IPv6 routing
  • Old connection string from before the PgBouncer/IPv4 deprecation

How to fix it

Try these in order — the most common fix is first.

  1. 1. Switch to the pooler connection string

    1. Dashboard > Connect
    2. Copy the Session pooler (port 5432) or Transaction pooler (port 6543) string
    3. Note the username format postgres.<project-ref>

  2. 2. Use transaction mode for serverless

    1. Pick port 6543 and disable prepared statements

  3. 3. Buy the IPv4 add-on if you need direct connections

    1. Project Settings > Add-ons > Dedicated IPv4 address

This guide also covers

  • supabase network is unreachable
  • supabase ipv6 connection
  • supabase could not translate host name
  • cannot connect to supabase database

Still not working?

If Supabase keeps failing, you're not alone. See every Supabase problem users report or the alternatives people switch to.

Other Supabase errors