Live

Builds failing in Southeast Asia (Singapore)

Builds fail in the Southeast Asia (Singapore) region of Railway. Railway reported the incident as resolved after 19 minutes. Builds are processing normally.

State

Resolved

Started

Lasted

19 min

Worst impact

Major outage

Timeline

3 updates
23:1023:1523:1923:2423:29
Major outagePartial outageUpdate postedTimes in UTC

Identified

19 min 100%

Updates

Times in UTC

As posted by Railway

Resolved

We have identified the issue affecting builds across all regions and have applied a fix. Builds are processing normally. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Identified

We are aware of an issue causing builds to fail across all regions. Users attempting to build may see their builds failing. We have identified the issue and are working on a fix. We will provide updates as we learn more.

Identified

We are aware of an issue causing builds to fail in our Southeast Asia (Singapore) region. Users attempting to build in this region may see their builds failing. We have identified the issue and are working on a fix. We will provide updates as we learn more.

Affected components

1
Southeast Asia (Singapore)

Railway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

58

Days with an incident

38

Median duration

1 h 19 min

This incident

76% shorter than the median

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

7 days
median 1 h 19 min
90 days agoToday

Other Railway incidents

All incidents

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