# Railway: External network blocks affecting access to Railway

> Railway reports that some users cannot access the Railway Dashboard at railway.com or Railway-hosted applications on public networking. Network providers and security services blocked Railway IP addresses. Railway has identified the problem and works with network providers and security vendors to remove the blocks. Railway gives no estimated time for the fix.

- Provider: [Railway](https://outages.cc/railway.md)
- Type: Incident
- State: identified
- Worst impact: Partial outage
- Started: 2026-11-04 18:54 UTC
- Components: Dashboard — railway.com, Networking — Public
- Official update: https://status.railway.com/incident/QBCLHG1V

## Updates from Railway

### identified, 2026-11-04 22:12 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.

### identified, 2026-11-04 22:09 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

### identified, 2026-11-04 22:06 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.

### identified, 2026-11-04 18:57 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