Hey there! We've found the following might help you get unblocked faster:

• 🧵 Connection Issue to PostgreSQL via Private Network (postgres.railway.internal)

• 🧵 Prisma deployment fails using internal Postgres URI

• 🧵 Railway IPv6 Outbound Connection Issue - Supabase PostgreSQL Connection Failing

If you find the answer from one of these, please let us know by solving the thread!

Can you enable Primsa debugging so we can see the underlying error?

DEBUG="prisma:*"

Here are the Prisma debug logs with DEBUG="prisma:*" enabled:

Error Code: P1001

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

prisma:client:libraryEngine sending request, this.libraryStarted: false

prisma:client:libraryEngine library starting

prisma:error Invalid prisma.landingRegion.findMany() invocation:

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

Additional info:

- Prisma Client version: 6.19.0

- External connection (switchback.proxy.rlwy.net:17764) works fine

- Internal DNS resolution seems to be failing

---

Is this intermittent or consistently reproducible?

Consistently reproducible.

The issue started at December 3rd, 2025, 12:00 PM KST

(03:00 UTC) and has been failing every time since then.

- Internal address (postgres.railway.internal:5432) →

always fails with P1001

- External address (switchback.proxy.rlwy.net:17764) →

always works

No code changes were made. It suddenly stopped working at

that specific time.

Currently using the external address as a temporary

workaround.

Hi. I'm having the exact same issue. Internal networking seems to not work at all in my new project. Using public Host & Port / URL works everytime. So far i've tried with a Mysql DB, Redis and MinIO service..
Can we get an official Railway response? It's been causing me massive headaches

I don't kwow.. and. I want to know!!!.. so angry!!!!!!!!!!!!!!!!!!!

Could you create your own threads and select the impacted service when doing so, please? This will help us track and aggregate these issues. Thank you

Not sure what you're on about, I was just raising awareness of the issue as it seems more people than me have been affected.
I've been trying to debug my service for a lot of hours now due to this issue, figured I might save time for someone else.

@ray-chen, i've created my own thread, thanks.

Hey there,

We might have rolled out a fix that would have fixed the issue.