Skip to main content
down.guideby Sazabi
Railway
DWN-e8b51fc050RailwayResolved

Deployments are slow to progress and are prone to timeout failure

Partial outage Lasted 1h 30m · started · Railway's page

Level
confirmed
Worst impact
Partial outage
Components
US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore), API - backboard.railway.com, Dashboard - railway.com, Login - GitHub
Regions
apac, eu, us
Down Index
40of 100

What to do

  • Check whether you use Railway US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) and 3 more in apac, eu, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

  • Confirm your retries, queues and scheduled jobs caught up after the 1h 30m it lasted.

    Anything that failed between 2026-08-19 01:00 UTC and 2026-08-19 02:30 UTC may need a replay.

  • Subscribe to Railway's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Railway 7

  1. investigating

    We are aware of an issue causing deployments to remain in an initializing state longer than expected. Users may experience delays in new deployments progressing. We are actively investigating and will provide updates as we learn more.

    provider

  2. investigating

    We are continuing to investigate and are narrowing down cause of delayed builds. Thanks for patience.

    provider

  3. investigating

    We are continuing to investigate and are narrowing down cause of delayed builds. Thanks for patience.

    provider

  4. investigating

    We are continuing to investigate and are narrowing down the cause of delayed and failing builds. Thank you for your patience.

    provider

  5. identified

    We have identified a load issue within our infrastructure affecting the ability for deployments and builds to progress. We have restored builds to Pro users, and are working to get to full capacity for all customers. We will continue to provide updates as the situation develops.

    provider

  6. monitoring

    Update: we are now seeing recovery of all build queues, however, a second order impact of the build queue is API response times increasing. API performance should restore once the queue is cleared. Trial/Hobby/Pro/Enterprise builds are all active and resumed. We'll monitor the situation and will provide further updates as we learn more.

    provider

  7. resolved

    We have observed recovery of builds and API back to nominal. Builds are progressing for everyone on the platform.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-e8b51fc050

Is Railway still down?

No, this incident was resolved 2026-08-19 02:30 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

1h 30m, from 2026-08-19 01:00 UTC to 2026-08-19 02:30 UTC, by the times Railway posted.

What was affected?

Railway named US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) and 3 more in apac, eu, us.

What caused it?

Railway hasn't published a root cause. If it does, it shows here.

Where does this come from?

Railway's official status page, https://status.railway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.

Sources

More from Railway

Feed