GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue.

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 4h 9m it lasted.

  Anything that failed between 2026-01-29 15:06 UTC and 2026-01-29 19: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 5

1. investigatingJan 29, 2026, 3:06 PM UTC

   GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue.

   provider

2. identifiedJan 29, 2026, 3:25 PM UTC

   We have disabled GitHub log in to reduce rate-limit pressure on the system.

   provider

3. identifiedJan 29, 2026, 5:38 PM UTC

   We have rolled out additional fixes to improve GitHub callpath resiliency. We are monitoring their effectiveness and will issue an update once we finish monitoring.

   provider

4. monitoringJan 29, 2026, 6:13 PM UTC

   We have observed no further GitHub rate limiting in the last 60 minutes and we are reanbling GitHub authentication.

   provider

5. resolvedJan 29, 2026, 7:15 PM UTC

   Our monitors have shown that we have good effect on our changes, although we have improvement, we are still monitoring the impact for all customers.

   provider

Corrections

None so far.

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