Hi, we are experiencing a production outage with a Railway Postgres database.

The Postgres service shows as online in the Railway dashboard, but our application services cannot connect to it through the private hostname:

postgres.railway.internal:5432

The issue started around 2026-06-19 09:00 UTC. Everything was working normally before that.

Errors from our app services include:

Prisma P1001: Can't reach database server at postgres.railway.internal:5432

connect ETIMEDOUT fd12:c4fe:dc9c:1:1000:77:12d6:a742:5432

When opening the database service in Railway and using Database Connection, it eventually fails with:

Connection terminated unexpectedly

The Postgres logs only show normal checkpoint messages and occasional client disconnects. I do not see Postgres crash/recovery/FATAL logs, and restarting the database service and app services did not resolve the issue.

This looks like a possible Railway private networking / internal IPv6 connectivity issue between services and the Postgres database.

Could you please check whether the private networking endpoint for this Postgres service is healthy? Thank you.