CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Webhooks
Affected components: WebhooksGit OperationsPull RequestsIssuesPackages
Timeline of updates
- investigating
We are investigating reports of degraded performance for Webhooks
- investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- investigating
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
- investigating
Packages is experiencing degraded performance. We are continuing to investigate.
- investigating
We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.
- monitoring
The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
- monitoring
We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.
- resolved
Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC.
Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC.
To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f1bad0953dbacd1e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2026-08-13 14:45 UTC, resolved after 51 min, 9 update(s).
- Title
- Incident with Webhooks
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/k8vbzwqjkxzn
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on August 13, 2026GitHub Copilot in August 2026MarkdownJSON