Update timeline
- investigating Mar 11, 2026, 02:25 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring Mar 11, 2026, 02:28 PM UTC
We are investigating degraded performance with Copilot Code Review. Customers may experience extended review times or occasional failures. We are seeing signs of improvement as our team works to restore normal service. We'll post another update by 15:30 UTC.
- monitoring Mar 11, 2026, 03:31 PM UTC
We experienced degraded performance with Copilot Code Review starting at 14:01 UTC. Customers experienced extended review times and occasional failures. Some extended processing times may continue briefly. We are monitoring for full recovery. We'll post another update by 16:30 UTC.
- monitoring Mar 11, 2026, 03:53 PM UTC
Copilot Code Review queue processing has returned to normal levels.
- resolved Mar 11, 2026, 03:53 PM UTC
On March 11, 2026, between 13:00 UTC and 15:23 UTC the Copilot Code Review service was degraded and experienced longer than average review times. On average, Copilot Code Review requests took 4 minutes and peaked at just under 8 minutes. This was due to hitting worker capacity limits and CPU throttling. We mitigated the incident by increasing partitions, and we are improving our resource monitoring to identify potential issues sooner.
Looking to track GitHub downtime and outages?
Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when GitHub reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track GitHub alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required