Resolved after 23 minutes, affecting US East (Virginia, USA) (Networking — Public (US East)) and US West (California, USA) (Networking — Public (US West)) and 1 more, on September 30, 2026.
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.
Affected components
Update timeline
- monitoring Sep 30, 2026, 07: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.
- resolved Sep 30, 2026, 08: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.
Your product runs on more than Railway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services