Railway favicon

Railway outage on 2026-11-08

railway.com
November 2026 8 Minor incident

If your builds on Railway failed to trigger on 8 November, the fault sat with GitHub, not Railway. Railway's status page logged the knock-on effect for 44h 35m, lasting into the next two days.

Started

10:11 UTC

Duration

Lasted 1d 20h

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 posted one update, at 10:11 UTC, under the title "GitHub Outage Affecting Builds". The text states that GitHub was experiencing an outage which caused build failures for projects using GitHub as a source. It also notes that deployments triggered manually or via CLI were unaffected, so the break was specific to the GitHub-sourced build path, not to Railway's deployment pipeline as a whole. The update adds that this issue was unrelated to the security incident from 21 October, which had already been resolved, a line included to head off confusion with an earlier event. Railway logged this as still open against that single 10:11 entry for 44h 35m, with no further update filed to close it out or explain GitHub's side in more detail. No components are listed as affected on Railway's own breakdown, consistent with the fault originating upstream at GitHub rather than inside Railway's infrastructure. No user reports were filed during the window on this record. Over the past 90 days Railway has logged 35 incidents with a median duration of 1 hour 50 minutes, so a 44h 35m duration is well outside the norm for this provider, though that length reflects how long the entry stayed open, not necessarily how long GitHub's own outage ran. One filing from a provider carries only as much detail as that provider chooses to give, and here Railway chose to give one paragraph and nothing more.

Learning

This outage sat one layer up from Railway itself: GitHub broke, and anything depending on GitHub as a build source broke with it, while manual and CLI deployments kept working because they never touched that path. If you only watch your own endpoints, or only watch Railway's deployment status, this kind of failure can be invisible until a build silently stalls. External checks hitting your live product would likely have stayed green throughout, because the product that was already deployed kept running, it was the next build that couldn't land. That is the general shape to recognise: a dependency of your provider fails, your provider's core service stays up, and the only visible symptom is builds or deploys that won't go through for a specific source path. Railway's own 30-day figures show 15 incidents, all resolved, with a median duration of 3h 53m, so a stuck update lasting almost two days stands out against their own baseline. 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.