Cursor reported this major-impact incident on its official status page on Aug 17, 2026, 14:34 UTC. It was resolved after 6h 6m.
Right now Cursor is operational. Live Cursor status →
The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service health.
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/)
We are currently investigating this issue. We will provide updates as more information becomes available.
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/
Our 5-minute checks didn't record a change in Cursor's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Cursor reported 50 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 8m. See Cursor's uptime and incident history