Resolved after 14 hours 46 minutes, on August 6, 2026.
We believe that this incident is largely mitigated. We still see an elevated job assignment latency for a small subset of jobs, but other symptoms have resolved meanwhile. GitHub is reporting their updates in https://www.githubstatus.com/incidents/qcvjkzcs7j74
Update timeline
- investigating Aug 06, 2026, 03:34 PM UTC
Upstream incident: https://www.githubstatus.com/incidents/qcvjkzcs7j74
- identified Aug 06, 2026, 03:55 PM UTC
We're seeing more widespread impact, with runners unable to acquire jobs. This is leading to increased queue times for a subset of jobs. GitHub is tracking this at https://www.githubstatus.com/incidents/qcvjkzcs7j74
- monitoring Aug 06, 2026, 10:06 PM UTC
We are seeing first signs of partial recovery but the incident is still ongoing and many jobs are still seeing elevated queue times. GitHub is tracking their updates in https://www.githubstatus.com/incidents/qcvjkzcs7j74
- monitoring Aug 07, 2026, 01:03 AM UTC
We believe that this incident is largely mitigated. We still see an elevated job assignment latency for a small subset of jobs, but other symptoms have resolved meanwhile. GitHub is reporting their updates in https://www.githubstatus.com/incidents/qcvjkzcs7j74
- resolved Aug 07, 2026, 06:20 AM UTC
All systems are operational.
Your product runs on more than Namespace
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services