Internal networking failure
filip-michalsky
PROOP

2 months ago

Hello,

Our production service experienced an outage where our production API service was unable to connect to our production database for about 60 minutes.

Roughly between

Mar 18, 2026 7:04:48 AM UTC

and

Mar 18, 2026 8:09:29 AM UTC.

Re-deploys were all failing as well for our postgres service.

We mitigated with railway agent which restarted both our API service and DB service at the same time.

Our sentry logs show:

ActiveRecord::ConnectionNotEstablished

connection to server at "fd12:697a:d5d0:0:2000:9:4e07:5dc8", port 5432 failed: Connection timed out (ActiveRecord::ConnectionNotEstablished)
	Is the server running on that host and accepting TCP/IP connections?

Note that I am pointing on the service - we were experiencing issues with this service @service:4b694c83-0b83-4833-a4dd-5d05c75d791c

in production environment.

It seems to be related to some internal railway issue.

how can we be sure that railway can provide reliable networking connections to the railway managed postgres?

Solved

1 Replies

Hey Filip, apologies for the disruption. We identified elevated connections on a single machine in our infrastructure that was causing intermittent internal networking failures during the window you described. The issue has been resolved. Your private network connections should be stable now. Let us know if you see any further issues.


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...