Issues with networking on a subset of hosts

What to do

• Check whether you use Railway DNS, EU West (Amsterdam, Netherlands), Traffic, US East (Virginia, USA) and 2 more in apac, eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 37m it lasted.

  Anything that failed between 2026-03-15 09:27 UTC and 2026-03-15 10:04 UTC may need a replay.

• Subscribe to Railway's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Railway 5

1. investigatingMar 15, 2026, 9:27 AM UTC

   We are currently investigating failures to reach the internet for a subset of deployments

   provider

2. investigatingMar 15, 2026, 9:32 AM UTC

   We were able to confirm impact to be limited to part of the fleet, but to be affecting all networking for affected deployments.

   provider

3. identifiedMar 15, 2026, 9:42 AM UTC

   We have identified the root cause and are working on a fix

   provider

4. monitoringMar 15, 2026, 9:52 AM UTC

   We implemented a fix and are currently monitoring the result.

   provider

5. resolvedMar 15, 2026, 10:04 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.