Outbound egress failure on US-East since ~06:35 UTC March 15 - all external connections timing out
codechr1s
PROOP

2 months ago

Since approximately 06:35 UTC on March 15, 2026, our production service on US-East has had zero outbound connectivity. The container runs fine and serves inbound HTTP requests, but ALL outbound connections fail with ENETUNREACH and ETIMEDOUT.

Affected services (all failing simultaneously):

- MongoDB Atlas — MongoServerSelectionError: Server selection timed out after 20000 ms

- PostHog proxy — AggregateError [ETIMEDOUT] on every request to us.i.posthog.com

- All other outbound HTTPS connections on port 443

The app was operating normally through 06:29 UTC (cron jobs, database queries, Redis jobs all completing successfully).

First errors appeared at 06:35:38 UTC with no code changes or deployments.

Errors include both IPv4 ETIMEDOUT and IPv6 ENETUNREACH to multiple unrelated external IPs, suggesting this is a platform-level egress issue rather than a destination-specific problem.

Redeploying resolved the issue (new replica got working networking), but the original replica never recovered on its own.

Project: 251e0394-2884-4914-a75e-bed972d19609

Service: 63f25f0d-18f5-4cbf-bcff-cdd7258ab7ec

Affected replica: 75816190-bc77-48f5-8dc0-27e6b9afbe94

Region: US-East

This appears related to the EU-West egress outage reported by another user starting at ~06:45 UTC, suggesting a platform-wide issue across multiple regions?

Can we confirm if there are issues?

Solved

8 Replies

ceotind
HOBBY

2 months ago

what's the point in using railway anymore. every other day they are down.


theashishchalke
HOBBY

2 months ago

I have the same issue on US East. Tried redeploy several times but to no avail. DNS and internal networking works fine. Egress Public networking fails. :

Project 55c28170-9e09-4562-875b-00383b5b9997

Service c44978a6-210e-4a46-8e39-2940c9036724

Region: US - East


2 months ago

Heya, we've called an incident here: https://status.railway.com/cmmrjwx4x0ltkf6zwi526b038 and are seeing recovery


Status changed to Awaiting User Response Railway 2 months ago


codechr1s
PROOP

2 months ago

Seeing the same issue as yesterday reappear right now.


Status changed to Awaiting Railway Response Railway 2 months ago


codechr1s
PROOP

2 months ago

Can anyone confirm the same?

Attachments


codechr1s

![](https://station-server.railway.com/attachments/att_01kktn9xktfzra71qa6b4mkxy5) Can anyone confirm the same?

Anonymous
PRO

2 months ago

yes. can confirm, same for us in AMS. redeploy fixed it for the time being, but how are we supposed to run reliable SaaS on RW if they keep having issues every week?


codechr1s
PROOP

2 months ago

Yep. Well this hit us only yesterday. Lucky I'm online and available to catch it. I'm starting to consider options also.

Outages and issues happen. But not having anyone immediately available to put out the flames is totally unacceptable.


sam-a
EMPLOYEE

2 months ago

We understand the frustration, and the feedback about response times during incidents is heard. We are continuing to work to minimize our response times as well as minimize disruptions. Sincere apologies.


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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...