Domain routing disruption

What to do

• Check whether you use Railway US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) 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 5m it lasted.

  Anything that failed between 2026-09-30 07:34 UTC and 2026-09-30 07:39 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.

Root cause

We are investigating the root cause and will provide updates as we learn more.

Updates from Railway 2

1. monitoringSep 30, 2026, 7:48 AM UTC

   We are aware of an issue that caused domains hosted on Railway to return 404 errors. The issue lasted approximately 5 minutes and has since been mitigated, this is a post facto report. We are investigating the root cause and will provide updates as we learn more.

   provider

2. resolvedSep 30, 2026, 8:17 AM UTC

   The global routing service provided a `not-found` response after a rollout of a network config change. The system self healed after the config change led to errors. Unfortunately, this led to observed impact to new connections to Railway hosted workloads for 5 minutes. There is no further and ongoing impact. The Networking team will be working on a full root cause and we will update this status report with a published cause.

   provider

Corrections

None so far.

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