Ted Hisokawa
Jun 11, 2025 21:08
In May 2025, GitHub experienced three major service disruptions affecting Issues, Actions, and Microsoft Teams integration. The incidents caused significant delays and outages impacting thousands of users.
GitHub, a leading platform for software development and version control, faced several service disruptions in May 2025, as reported by Jakub Oleksy on the official GitHub blog. These incidents impacted multiple services, leading to degraded performance and outages that affected thousands of users globally.
Issues Service Disruption
On May 1, 2025, from 22:09 UTC to 23:13 UTC, GitHub’s Issues service experienced degraded performance. This was due to a new feature that introduced a custom header in client-side HTTP requests, resulting in CORS errors during attachment uploads. Approximately 130,000 users were impacted for around 45 minutes. The problem was mitigated by rolling back the feature flag and implementing new metrics to monitor client-side requests.
GitHub Actions Delay
On May 28, 2025, GitHub Actions encountered delays in job starts for workflows using Ubuntu-24 standard hosted runners. The issue, lasting from 09:45 UTC to 14:45 UTC, was caused by a backend caching misconfiguration after a failover, leading to duplicate job assignments. This affected 19.7% of Ubuntu-24 hosted runner jobs on public repositories. The issue was resolved by updating the backend cache and scaling up runner pools to clear the backlog.
Microsoft Teams Integration Outage
On May 30, 2025, the Microsoft Teams GitHub integration service faced a complete outage from 08:10 UTC to 16:00 UTC. The outage, resulting in a 100% error rate, was attributed to an authentication issue with a downstream provider. Despite having monitoring in place, the alert thresholds were insufficient, delaying incident detection. GitHub worked with the provider to restore functionality and plans to migrate to more robust authentication methods.
These incidents highlight the challenges of maintaining seamless service in complex technological environments. GitHub has taken steps to prevent future occurrences by enhancing monitoring and authentication processes. For ongoing updates, users can visit the GitHub status page.
Image source: Shutterstock
Credit: Source link
