Railway favicon

Railway outage on 2026-10-23

railway.com
October 2026 23 Minor incident

Railway's support and community site, station.railway.com, was unavailable for 124h 15m starting 22:03 UTC on 23 October. The outage and the account signup freeze that came with it were on Railway's side, not yours.

Started

22:03 UTC

Duration

Lasted 5d 4h

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?

The record shows a single incident on this day, affecting station.railway.com, Railway's support and community property. It started at 22:03 UTC and ran for 124h 15m. Railway filed one update across the whole window. That update says the site is "now restored" and that support threads can be raised again on it, and that the team has caught up with most support requests. The same update says new account signups remain paused and some non-essential product features remain disabled, with a promise to update the notice as functionality restores. No components are listed against this incident in the record, and no further updates were filed after this one. No user reports were logged during the window. Because only one filing exists for a period spanning over five days, there is no way to say from this record how long the site was actually down versus how long the surrounding signup freeze lasted, or whether they ended at the same time. Railway's status page does not say what caused the outage or the freeze. No post-mortem has been published.

Learning

This incident sat on Railway's support infrastructure, not on the platform that runs your deployed services, and that is a layer your own uptime checks on your product would never touch. If you were only watching your own endpoints, they would have stayed green through this whole thing, correctly, because your application tier was never the thing that broke. Railway's own status reporting here was thin: one update for a five-day-plus window, with the start and end of the actual outage blurred into a single notice about support and signups. That is a common shape for provider-side incidents, where the vendor's own words are the only record available and a single filing has to carry the whole story. Over the last 90 days Railway has logged 35 incidents with a median duration of 1 hour 30 minutes, so an incident running past five days is well outside their typical pattern. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.