GitHub-triggered builds are delayed

What to do

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

  Anything that failed between 2026-10-05 14:30 UTC and 2026-10-05 16:45 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 4

1. investigatingOct 5, 2026, 2:55 PM UTC

   We are aware of an issue affecting builds triggered by GitHub. Users may experience builds queuing or taking longer than usual to start. We are actively investigating the root cause and will provide updates as we learn more.

   provider

2. identifiedOct 5, 2026, 3:40 PM UTC

   We've identified the issue and are working on a fix. We will continue to provide updates as we learn more.

   provider

3. monitoringOct 5, 2026, 3:52 PM UTC

   We are seeing recovery and the build queue is continuing to drain. GitHub-triggered builds may still take longer than usual to start while we work through the remaining backlog. We will provide another update as we make further progress.

   provider

4. resolvedOct 5, 2026, 4:13 PM UTC

   The issue affecting GitHub-triggered builds has been resolved. The build queue has fully drained and 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.

   provider

Corrections

None so far.

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