Provider incident title: “Incident with Pull Requests”
Started
Thursday, April 23, 2026
07:50 PM UTC
Duration
1h 52m
total
Resolved
09:43 PM UTC
Apr 23, 2026
We are investigating reports of degraded performance for Pull Requests
We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.
Pull Requests is operating normally.
We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC. <br /><br />This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
GitHub Copilot is back online
View current status and uptime history
GitHub Copilot 30-day uptime: 98.1% based on Tickerr's independent monitoring checks.
This incident was sourced from GitHub Copilot's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted 1h 52m.
Tickerr monitors 90+ AI tools independently. View live GitHub Copilot status or all AI tool status.
Get alerted next time GitHub Copilot goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Join developers tracking AI tool costs and uptime — every Monday.
Also on Tickerr