GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers.

What to do

• Check whether you use Railway GitHub - Auto-Deploys. 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 6h 18m it lasted.

  Anything that failed between 2026-01-28 18:02 UTC and 2026-01-29 00:20 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 6

1. investigatingJan 28, 2026, 6:02 PM UTC

   GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers.

   provider

2. identifiedJan 28, 2026, 6:41 PM UTC

   We are implementing workarounds to increase GH throughput to prevent GH ratelimiting.

   provider

3. identifiedJan 28, 2026, 7:12 PM UTC

   Customers report recovery in most GH operations, waiting to merge long term fixes until resolving the incident.

   provider

4. identifiedJan 28, 2026, 9:20 PM UTC

   We have temporarily disabled GitHub logins while we work to reduce load on the GH downstream endpoints to regain quota.

   provider

5. monitoringJan 29, 2026, 12:06 AM UTC

   We have restored GitHub logins for everyone. We are monitoring the performance and recovery for all customers.

   provider

6. resolvedJan 29, 2026, 12:20 AM UTC

   We have confirmed that GitHub login, and repo access is working for all customers on the platform. We apologize for the impact and we will publish a public retro.

   provider

Corrections

None so far.

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