Railway incident
GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers.
Resolved after 6 hours 17 minutes, affecting External & Third-Party Integrations (GitHub — Auto-Deploys), on January 28, 2026.
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.
Affected components
Update timeline
- investigating Jan 28, 2026, 06:02 PM UTC
GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers.
- identified Jan 28, 2026, 06:41 PM UTC
We are implementing workarounds to increase GH throughput to prevent GH ratelimiting.
- identified Jan 28, 2026, 07:12 PM UTC
Customers report recovery in most GH operations, waiting to merge long term fixes until resolving the incident.
- identified Jan 28, 2026, 09:20 PM UTC
We have temporarily disabled GitHub logins while we work to reduce load on the GH downstream endpoints to regain quota.
- monitoring Jan 29, 2026, 12:06 AM UTC
We have restored GitHub logins for everyone. We are monitoring the performance and recovery for all customers.
- resolved Jan 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.
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.
Amazon Web Services