Railway incident

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.

Resolved after 4 hours 8 minutes, affecting External & Third-Party Integrations (GitHub — Auto-Deploys), on January 29, 2026.

resolved Jan 29, 2026, 07: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.

Started
Jan 29, 2026, 03:06 PM UTC
Resolved
Jan 29, 2026, 07:15 PM UTC
Duration
4h 8m
Detected by Pingoru
Jan 29, 2026, 03:06 PM UTC

Affected components

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

Update timeline

  1. investigating Jan 29, 2026, 03: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.

  2. identified Jan 29, 2026, 03:25 PM UTC

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

  3. identified Jan 29, 2026, 05: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.

  4. monitoring Jan 29, 2026, 06:13 PM UTC

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

  5. resolved Jan 29, 2026, 07: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.

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 →