Contact Railway support with:

• Project ID: 65ba0f37-e1cd-439c-a11d-cfa8d029ed62
• Environment: production
• Service: Postgres (ID: 41c4c20b-bf18-40c4-92dc-37699703cd0b)
• Region: asia-southeast1-eqsg3a
• Issue: TCP proxy completely broken, railway connect fails, internal connections also failing
• What you've tried: restarted, redeployed, recreated TCP proxies multiple times
• Critical: Data loss is not acceptable

They have backend access to the infrastructure and can either restore connectivity or safely migrate your data to a new region without data loss.

This is beyond what I can fix from the platform API. You need their infrastructure team.

Which service is trying to connect?

Not a Railway service — connecting from a local machine (macOS) to the Postgres service's TCP proxy for a data export.

What error?

Connection refused

(errno 61) on every TCP proxy endpoint. The Postgres service is ACTIVE and accepting internal connections (the

unique-commitment

app service connects fine via

postgres.railway.internal:5432

), but no public TCP proxy works.

How are you connecting?

psql "postgresql://postgres:password@switchyard.proxy.rlwy.net:59162/railway"

What we've tried:

- 3 different TCP proxy endpoints:

junction.proxy.rlwy.net:45678

,

maglev.proxy.rlwy.net:53262

,

switchyard.proxy.rlwy.net:59162

— all refuse connections - Restarted Postgres service - Redeployed Postgres service - Deleted and recreated TCP proxies multiple times - DNS resolves fine, ports 80/443 on the proxy hosts are reachable, only the assigned TCP proxy ports refuse - Postgres logs show

database system is ready to accept connections

- Region:

asia-southeast1-eqsg3a

-

railway connect postgres

also fails with the same error (it uses the TCP proxy under the hood)