Cursor · 57d ago
GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase
ResolvedYes — Cursor had a problem on August 17, 2026, and Cursor has since marked it resolved. Cursor's latest word: “The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service health.”
Timeline
Started: 8/17/2026, 2:34:00 PM
Last update: 8/17/2026, 8:40:02 PM
Resolved: 8/17/2026, 8:40:02 PM
Affected: k0trcq273dr6, 2x2chyqwmkzl, mwv1g9sc7kdh, xwjpvdf81qh9
Updates
resolved
The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service health.
8/17/2026, 8:40:02 PM
investigating
We’re seeing signs of recovery, consistent with our upstream dependency’s latest status updates. We’re continuing to monitor our service health and GitHub's upstream status (https://www.githubstatus.com/)
8/17/2026, 7:43:33 PM
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
8/17/2026, 3:25:14 PM
investigating
We are investigating a service degradation affecting Automations, Cloud Agents, Review Agents and Codebase related to a GitHub degradation reported in GitHub's status page: https://www.githubstatus.com/
8/17/2026, 2:34:40 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 14h ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago
- Elevated errors affecting Opus 5.5 — resolved, 5d ago
- Opus 5.5 is Experiencing 429s — resolved, 5d ago
- Investigating service degradation — Grok Bot — resolved, 6d ago