On August 17, 2026, Cursor reported a service degradation that impacted its Automations, Cloud Agents, and Codebase components. The outage was traced to an upstream issue at GitHub, as indicated on GitHub’s status page. The incident began at 15:25 UTC and was initially flagged as “Investigating.” By 19:43 UTC, the team confirmed the degradation and began monitoring both Cursor’s internal metrics and GitHub’s external status updates.

The company’s response included continuous updates: by 20:40 UTC, they reported signs of recovery and confirmed that the affected services had recovered. Cursor will continue to monitor service health and will provide further updates if any new issues arise. The restoration was attributed to GitHub’s resolution of the underlying problem, which is reflected in their latest status dashboard.

Customers using Cursor features for automation and code review can expect normal operation moving forward. The incident highlights the importance of monitoring external dependencies in real‑time and maintaining transparent communication with users during outages.

The degradation lasted roughly four hours, with the last update at 20:40 UTC confirming full recovery. Cursor’s incident response team employed automated health checks and cross‑team communication to expedite the resolution. Post‑incident analysis will focus on enhancing dependency monitoring dashboards and updating the incident playbook to reduce detection time.