Deployment queue backlog after the October 21 security incident (record added Nov 5)

What to do

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

  Anything that failed between 2026-10-22 06:30 UTC and 2026-10-22 16:15 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 2

1. identifiedOct 22, 2026, 6:30 AM UTC

   Deployments queued at up to 47,000 (normal about 1,000) and started slowly until the backlog cleared at about 16:10 UTC. Record added on November 5, 2026 from the incident review that followed the October 21 security incident. This entry corrects the uptime record; no notification was sent for it.

   provider

2. resolvedOct 22, 2026, 4:15 PM UTC

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

   provider

Corrections

None so far.

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