CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Issues, API Requests and Pull Requests
Timeline of updates
- resolved
Starting on May 7th, 2024 at 14:00 UTC, our elasticsearch cluster that powers Issues and Pull Requests became unresponsive correlating to a spike in usage. This affected GitHub customers who were trying to search issues and pull requests. We mitigated this incident by adding additional cluster members which increased the resources available to the cluster. We are working to add additional safeguards to our endpoints. We are also continuing to investigate the root cause of the instability and if the index needs to be re-sharded for future risk mitigation.
From GitHub Copilot’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2024-05-07 14:23 UTC, resolved after 1.5 h, 1 update(s).
- Title
- Incident with Issues, API Requests and Pull Requests
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/tsrh60nkbchl
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on May 7, 2024GitHub Copilot in May 2024MarkdownJSON