CircleCI: GitHub service degradation may impact customers using GitHub
GitHub outage, Jul 24, 2026 · 9 vendors, 12 incidents
CircleCI’s incident blames GitHub as the cause. (hop 1, posted +19 min vs GitHub’s own post)
“…GitHub service degradation may impact customers using GitHub The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/i…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 16:17 UTC"]:::root
h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>Bolt.new, CircleCI"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed GitHub<br/>Bolt.new"]:::blames
root --> h4
me["CircleCI (this incident)<br/>posted +19 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Pipelines & Workflows
Timeline of updates
- identified
GitHub is currently experiencing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m). Customers who use GitHub as their VCS may experience impact to their CircleCI platform experience as a result, impacting checkout and workflows. We will provide another update as we have more information to share. Thank you for your patience.
- resolved
The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).