Skip to main content
down.guideby Sazabi
Railway
DWN-26c02b96f1RailwayResolved

Deployment slowness

Partial outage Lasted 5h 31m · started · Railway's page

Level
confirmed
Worst impact
Partial outage
Components
EU West (Amsterdam, Netherlands), US East (Virginia, USA), Southeast Asia (Singapore), US West (California, USA)
Regions
apac, eu, us
Down Index
43of 100

What to do

  • Check whether you use Railway EU West (Amsterdam, Netherlands), US East (Virginia, USA), Southeast Asia (Singapore), US West (California, USA) 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 5h 31m it lasted.

    Anything that failed between 2026-03-10 15:19 UTC and 2026-03-10 20:49 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 11

  1. investigating

    We are currently investigating an issue causing deployments to take longer than normal

    provider

  2. identified

    We've pushed out a fix and are seeing slow recovery.

    provider

  3. monitoring

    We're seeing recovery, with delays primarily impacting trial deployments. We are monitoring for full recovery.

    provider

  4. monitoring

    We are continuing to monitor this incident. Deployments may be queued, but are going through

    provider

  5. monitoring

    Our team continues to work on this incident. Deploys are still slow, but not failing.

    provider

  6. monitoring

    Deployment slowness is persisting. Deploys are completing but with longer than normal queue and build times. Our team is actively working on a resolution.

    provider

  7. monitoring

    Elevated load continues to cause slowness on our system. We're pausing Free, Trial and Hobby deployments to assist with deployment backpressure.

    provider

  8. monitoring

    Elevated load continues to cause slowness on our system. We' have restored all Pro deployments back to nominal, we are turning on Hobby slowly to assist with deployment backpressure.

    provider

  9. monitoring

    We've successfully eliminated slowness from our deployment pipeline, and are re-enabling deployments for all plans as the backpressure is recovering.

    provider

  10. monitoring

    We are seeing improvement — deployments are now processing without being queued. We continue to monitor the situation and will provide a further update once we are confident the issue is fully resolved

    provider

  11. resolved

    This incident has been resolved.

    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-26c02b96f1

Is Railway still down?

No, this incident was resolved 2026-03-10 20:49 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

5h 31m, from 2026-03-10 15:19 UTC to 2026-03-10 20:49 UTC, by the times Railway posted.

What was affected?

Railway named EU West (Amsterdam, Netherlands), US East (Virginia, USA), Southeast Asia (Singapore), US West (California, USA) 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