# Disruption with some GitHub services

- Provider: [GitHub](https://down.guide/github)
- Level: confirmed
- Impact: Degraded
- lasted 2h 50m
- started 2026-04-22 19:53 UTC
- Issues
- id: DWN-b8f06bc261
- Official page: https://stspg.io/xmhs8h2d6zlj

## Updates from GitHub
### 2026-04-22 19:53 UTC: investigating
We are investigating reports of impacted performance for some GitHub services.

### 2026-04-22 19:55 UTC: investigating
Issues is experiencing degraded performance. We are continuing to investigate.

### 2026-04-22 20:02 UTC: investigating
Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

### 2026-04-22 20:37 UTC: investigating
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.

### 2026-04-22 22:09 UTC: investigating
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

### 2026-04-22 22:43 UTC: resolved
On April 22, 2026, between 09:00 UTC and 22:05 UTC, the Copilot coding agent and pull request comment event processing were degraded. During this period, approximately 0.5% of total pull request and issue comments mentioned @copilot (~23,000 invocations), explicitly requested work from the Copilot coding agent but were not acted upon.
Creating, viewing, and replying to pull request comments was unaffected, and other Copilot
functionality continued to operate normally. The impact was limited to @copilot mentions on pull request comments not triggering Copilot coding agent runs, and to some downstream systems not receiving new pull request comment events during the impact window.
The cause was a serialization error that prevented pull request comment events from being published to downstream consumers, including the Copilot coding agent. This was related to the same class of issue as incident #4295 on April 20, affecting a another event type.
We mitigated the incident by deploying a fix that restored event publishing, after which the Copilot coding agent and other downstream consumers resumed processing pull request comment events normally.
We are working to complete our audit of related event schemas, migrate remaining consumers to use
the updated identifier fields, and improve monitoring to detect drops in publishing on critical event topics, to reduce our time to detection and mitigation of issues like this one in the future.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).