External network blocks affecting access to Railway

What to do

• Check whether you use Railway Dashboard - railway.com, US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands) and 1 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 4d 23h it lasted.

  Anything that failed between 2026-11-04 18:54 UTC and 2026-11-09 18:03 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 4

1. identifiedNov 4, 2026, 6:54 PM UTC

   Some users are unable to access Railway-hosted applications or railway.com because network providers and security services have blocked Railway IP addresses. We’ve confirmed that a third party is sending scanning traffic using forged Railway source IP addresses. This traffic does not originate from Railway’s network. The spoofing does not require access to Railway infrastructure, and these reports are not evidence that Railway services or customer workloads have been compromised. We have found no evidence that this is in any way tied to the October 21 security incident. We are working with network providers and security vendors to remove the resulting blocks and correct reputation listings. Access may remain affected on individual networks until those blocks are lifted. If you are affected, ask your network administrator or provider to review any blocks on Railway IP addresses and share this incident notice with them. They can allow legitimate access to your application while retaining protections against unsolicited scanning traffic. Using another network may provide temporary access. We will provide updates as this work progresses.

   provider

2. identifiedNov 4, 2026, 10:03 PM UTC

   Access remains affected from some networks that are blocking Railway IP addresses. We have submitted review requests to security vendors and continue working with network operators to restore legitimate access. The scanning traffic uses forged Railway source IP addresses and does not originate from our network. We do not yet have an estimated time for all affected networks to remove their blocks. Network administrators can use this incident notice to review affected rules and permit legitimate access while retaining protections against unsolicited scanning traffic.

   provider

3. identifiedNov 5, 2026, 6:51 PM UTC

   Some users are reporting restored access to Railway-hosted services. We have contacted network operators, security vendors and abuse database providers, and continue working to resolve the remaining access issues. Access remains affected from some networks. Using another network may provide temporary access. We’ll provide further updates as this work progresses.

   provider

4. resolvedNov 9, 2026, 6:03 PM UTC

   We have worked with network operators and security vendors to address blocks applied by external networks to Railway-hosted services. Following the recovery reported by affected users, we are closing this incident. Thank you for your patience while we worked to restore access.

   provider

Corrections

None so far.

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