outages.live
Live
RailwayIncident ·

GitHub Outage Affecting Builds

DegradedOfficial update
0

Railway reports build failures for projects that use GitHub as a source. Auto-deploys are degraded. Railway is monitoring the situation. Deployments that users trigger manually or by CLI are not affected.

State

Triage

Started

Ongoing for

42 h 42 min

Worst impact

Degraded

Timeline

1 update
Nov 8Nov 8Nov 9Nov 9Nov 10
DegradedUpdate postedDates in UTC

Triage

42 h 42 min 100%

Updates

Times in UTC

As posted by Railway

Triage

We are aware that GitHub is currently experiencing an outage which is causing build failures for projects using GitHub as a source. Deployments triggered manually or via CLI are unaffected. We are monitoring the situation and will provide updates as GitHub works to restore service. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.

Affected components

1
GitHub - Auto-Deploys

Railway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

62

Days with an incident

40

Median duration

1 h 28 min

This incident

29× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 1 h 28 min
90 days agoToday

Other Railway incidents

All incidents

Railway·External network blocks affecting access to Railway

Railway reports that users cannot access Railway-hosted applications and railway.com. The Dashboard and the regions US East, US West, EU West, and Southeast Asia were affected. Railway says the incident is resolved and lasted about 5 days.

Resolved

Railway·US East build failures (record added Nov 5)

Resolved. This entry was added on November 5, 2026 to correct the record.

Resolved

Railway·Elevated Build Failure Rate

The elevated build failure rate has been resolved. Builds are processing normally across all regions. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.

Resolved

Railway·US East build failures after the queue was released (record added Nov 5)

Resolved. This entry was added on November 5, 2026 to correct the record.

Resolved

Railway·Deployments paused (record added Nov 5)

Resolved. This entry was added on November 5, 2026 to correct the record.

Resolved

Follow Railway

Your coding agent knows when Railway is down, and tells you when a failure is theirs, not yours. You can also get Railway incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "railway" and tell me if Railway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=railway
Slack
/feed subscribe https://outages.live/feed.xml?providers=railway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane