# GitHub Copilot: Incident with Pull Requests, Git Operations, Actions, API Requests, Issues and Webhooks

> GitHub Copilot status incident “Incident with Pull Requests, Git Operations, Actions, API Requests, Issues and Webhooks” on 2024-04-24: impact minor (vendor’s label), 5.5 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg
Last updated: 2024-04-24T16:16:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2024-04-24 10:45 UTC · Resolved: 2024-04-24 16:16 UTC · Duration: 5.5 h
- Updates: 1
- [Vendor status page: https://www.githubstatus.com/incidents/7txcg0j03kkg](https://www.githubstatus.com/incidents/7txcg0j03kkg)
- [Company: GitHub Copilot](https://rewindex.com/company/github-copilot.md)

## Timeline of updates

- **resolved** 2024-04-24 16:16 UTC: On April 24, 2024, between 10:26 and 16:30 UTC, the Pull Request page took longer than usual to enable a Pull Request to be merged. During the incident, the 75th percentile time to merge a pull request went from around 3 seconds to just over 6 minutes. We also saw slightly elevated error rates across the service, with an average error rate of 0.1%, peaking to 0.31% of requests. The underlying cause of the incident was a repeated problematic query that resulted in MySQL replicas crashing, which caused a back-up in the jobs that compute whether PRs can be merged. At 16:30 the incident self-mitigated when the volume of the problematic query decreased. Concurrent to this, we deployed a mitigation to remove the mergability polling code from the PR experience to alleviate pressure on MySQL servers. This mitigation caused the merge button to not automatically enable, but require a page refresh instead. At 17:40 we statused PRs again for this issue. We rolled back the mitigation to resolve the second incident at 18:20. Going forward, to improve mitigation we are investing in faster recovery from cascading read-replica crashes, improving query retry logic to more aggressively back off when read replicas are unhealthy, improving our ability to diagnose server crashes and trace them back to user activity, and making it easier to block problematic queries. To prevent recurrence, we are eliminating the query that caused the server to crash, improving our detection and mitigation of problematic queries, and investigating and remediating the underlying issues that caused MySQL to crash. We are also improving the merge button polling mechanism and mergeability background job to be resilient to this class of incident so customers can still merge PRs.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2024-04-24 10:45 UTC, resolved after 5.5 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg
- Citation: GitHub Copilot, “Incident with Pull Requests, Git Operations, Actions, API Requests, Issues and Webhooks” (2024-04-24 10:45 UTC). Archived by Rewindex: https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg (CC BY 4.0).
- Markdown link: `[GitHub Copilot: Incident with Pull Requests, Git Operations, Actions, API Requests, Issues and Webhooks (2024-04-24)](https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg)`


---
Canonical: https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg · Markdown: https://rewindex.com/company/github-copilot/incidents/7txcg0j03kkg.md · JSON: https://rewindex.com/api/v1/companies/github-copilot/incidents/7txcg0j03kkg · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:33:29.086Z