Disruption with some GitHub services

What to do

• Check whether you use GitHub Issues. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 50m it lasted.

  Anything that failed between 2026-04-22 19:53 UTC and 2026-04-22 22:43 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 6

1. investigatingApr 22, 2026, 7:53 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. investigatingApr 22, 2026, 7:55 PM UTC

   Issues is experiencing degraded performance. We are continuing to investigate.

   provider

3. investigatingApr 22, 2026, 8:02 PM UTC

   Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.

   provider

4. investigatingApr 22, 2026, 8:37 PM UTC

   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.

   provider

5. investigatingApr 22, 2026, 10:09 PM UTC

   We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.

   provider

6. resolvedApr 22, 2026, 10:43 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.