GitHub integration: intermittent deploy failures

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 3h 34m it lasted.

  Anything that failed between 2026-05-23 16:11 UTC and 2026-05-23 19: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 5

1. identifiedMay 23, 2026, 4:11 PM UTC

   GitHub is experiencing intermittent errors with app installation token authentication: https://www.githubstatus.com/incidents/k5z4d1v1tqmt. This may cause "Bad credentials" or "repository not authorized" errors when deploying from GitHub. Deploys should recover as GitHub resolves this upstream issue.

   provider

2. identifiedMay 23, 2026, 5:06 PM UTC

   GitHub continues to investigate elevated authentication failures for app installation tokens. Deploys from GitHub may intermittently fail with "Bad credentials" errors. We're monitoring and will update when GitHub resolves this.

   provider

3. identifiedMay 23, 2026, 5:47 PM UTC

   GitHub is seeing signs of mitigation and is continuing to monitor for complete mitigation.

   provider

4. monitoringMay 23, 2026, 7:05 PM UTC

   GitHub is seeing significant signs of mitigation and monitoring for full mitigation.

   provider

5. resolvedMay 23, 2026, 7:45 PM UTC

   The GitHub incident has been resolved.

   provider

Corrections

None so far.

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