Railway incident

GitHub integration: intermittent deploy failures

Resolved after 3 hours 34 minutes, affecting External & Third-Party Integrations (GitHub — Auto-Deploys), on May 23, 2026.

monitoring May 23, 2026, 07:05 PM UTC

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

Started
May 23, 2026, 04:11 PM UTC
Resolved
May 23, 2026, 07:45 PM UTC
Duration
3h 34m
Detected by Pingoru
May 23, 2026, 04:11 PM UTC

Affected components

External & Third-Party Integrations (GitHub — Auto-Deploys)

Update timeline

  1. identified May 23, 2026, 04: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.

  2. identified May 23, 2026, 05: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.

  3. identified May 23, 2026, 05:47 PM UTC

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

  4. monitoring May 23, 2026, 07:05 PM UTC

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

  5. resolved May 23, 2026, 07:45 PM UTC

    The GitHub incident has been resolved.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →