tickerr
Degraded PerformanceResolvedOfficial report

Incident with Pull Requests: High percentage of 500s

Started

Tuesday, March 31, 2026

03:05 PM UTC

Duration

6h 18m

total

Resolved

09:23 PM UTC

Tuesday, March 31, 2026

Incident update

On Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures. On average, the error rate was 0.15% and peaked at 0.28% of requests to the service. This was due to a change in garbage collection (GC) settings for a Go-based internal service that provides access to Git repository data. The changes caused more frequent GC activity and elevated CPU consumption on a subset of storage nodes, increasing latency and failure rates for some internal API operations.<br /><br />We mitigated the incident by reverting the GC changes. To prevent future incidents and improve time to detection and mitigation, we are instrumenting additional metrics and alerting for GC-related behavior, improving our visibility into other signals that could cause degraded impact of this type, and updating our best practices and standards for garbage collection in Go-based services.<br />

GitHub Copilot is back online

View current status and uptime history

GitHub Copilot status →

Other GitHub Copilot incidents

Degraded Performance
Disruption with some GitHub services
Apr 14, 2026
Major Outage
Incident with Pages
Apr 13, 2026
Degraded Performance
Disruption with some GitHub services
Apr 13, 2026
Degraded Performance
Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard
Apr 10, 2026
Major Outage
Disruption with some GitHub services
Apr 9, 2026

View all GitHub Copilot incident history →