Domain routing disruption

Timeline

1. 07:34 UTC Railway status page · Reported Domain routing disruption
2. 07:48 UTC Railway status page · Monitoring 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.
3. 08:17 UTC Railway status page · Resolved 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.