Partial Degradation in Issues Experience
Incident
Report for GitHub
Resolved
On June 18, 2025, between 15:15 UTC and 19:29 UTC, the Issues service was degraded, and certain GraphQL queries accessing the `ReactionGroup.reactors` field returned errors. Our query routing infrastructure was impacted by exceptions from a particular database migration, resulting in errors for an average of 0.0097% of overall GraphQL requests (peaking at 0.02%).
We mitigated the incident by reverting the migration.
We continue to investigate the cause of the exceptions and are holding off on similar migrations until the underlying issue is understood and resolved.
We mitigated the incident by reverting the migration.
We continue to investigate the cause of the exceptions and are holding off on similar migrations until the underlying issue is understood and resolved.
Update
We have confirmed that we are currently within SLA for Issues experience. Remaining clean up will complete over the next few hours to fully restore the ability to search Issues by reaction as well as related GraphQL API queries.
Update
We have confirmed that impact is restricted to failing to display reactions on some issues and searching issues by reaction. Mitigation is in progress to restore these features and should be fully rolled out to all customers in the next few hours.
Update
Some users are seeing errors when accessing issues on GitHub. We have identified the problem and are working on a revert to restore full functionality.
Investigating
We are investigating reports of degraded performance for Issues
This incident affected: Issues.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe