Builds failed in Railway's US West and US East regions for 36 minutes on 13 November 2026. Railway traced the fault to a Cloudflare DNS resolver that went briefly unavailable on their end, not to anything in your project.
Started
23:25 UTC
Duration
Lasted 36m
Source
IsDown
Next time
Railway is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Railway's status page logged one incident on this day, starting at 23:25 UTC and lasting 36 minutes in total. The title given was "Builds failing in US West & US East", and the first update at 23:25 said Railway was aware of an issue causing build failures in those two regions and was investigating. At 23:38 UTC, Railway posted a second update explaining that Cloudflare's DNS resolver had been briefly unavailable, which caused the build failures, and that Railway had switched to an alternate resolver and builds had recovered. That second update is marked MONITORING rather than resolved, but no further update was filed after it, and the total duration recorded is 36 minutes. No components are listed as affected in Railway's own breakdown for this incident. No user reports were filed during the window, so there is no independent account of what builds looked like from the outside while this was happening. Railway's explanation rests on that single update from their side, and nothing further has been published to confirm or add to it. Over the past 90 days Railway has logged 35 incidents with a median duration of 1 hour 50 minutes, which makes this one shorter than typical. Across all time Railway has recorded 566 incidents, averaging 10.3 per month.
Learning
This incident sat in the build pipeline, not in a web-facing endpoint, so it is the kind of fault that a simple uptime check against your live site or API would never see. If your builds were failing in US East or US West during this window, your deployed app could have stayed up and answering requests the whole time, because the failure was happening before anything reached production. That is a different layer from what most monitoring watches, and it shows why a clean dashboard on your own service does not mean the platform underneath it is behaving. Railway's own fix was to switch DNS resolvers, which is a provider-side change you have no visibility into and no ability to trigger yourself. Over the last 30 days UptimeRobot's own checks against Railway logged 15 incidents with a median duration of 3 hours 53 minutes, a different picture from what Railway's own page shows for the same period, which is the expected result of checking from outside rather than relying on the vendor's self-reporting. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.