- Updated: March 25, 2026
- 2 min read
GitHub Services Degraded Performance on March 24, 2026 – Full Incident Overview
GitHub Services Degraded Performance on March 24, 2026 – Full Incident Overview
On March 24, 2026, GitHub experienced a significant service incident that impacted a wide range of core features, including GitHub Actions, Issues, Pull Requests, Webhooks, and several other components of the platform. The outage began in the early hours UTC and triggered degraded performance across the affected services for several hours.
Timeline of the Incident
- 00:45 UTC – Monitoring systems detected abnormal latency in GitHub Actions runners.
- 01:10 UTC – Issues and Pull Request APIs started returning delayed responses.
- 02:05 UTC – GitHub engineering teams identified a cascading failure in the internal event processing pipeline.
- 04:30 UTC – Mitigation steps were applied, gradually restoring normal service levels.
- 06:15 UTC – Full functionality confirmed, and the incident was declared resolved.
Impact on Users
During the incident, developers reported:
- Slower execution times for GitHub Actions workflows.
- Delays when creating or updating Issues and Pull Requests.
- Intermittent failures in webhook deliveries, affecting third‑party integrations.
Root Cause and Resolution
The root cause was traced to a bottleneck in the event‑processing service that handles real‑time updates across GitHub’s infrastructure. A misconfiguration caused queue congestion, leading to the observed latency. The engineering team rolled back the recent configuration change and introduced additional queue monitoring to prevent recurrence.
What’s Next?
GitHub has committed to improving its event‑processing resilience and will publish a detailed post‑mortem later this week.
For the official incident report, visit the GitHub Status page. For more guidance on handling GitHub outages, read our related articles: