Major impactResolvedAI/ML

Cursor outage: GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase

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 →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Aug 17, 2026, 14:34 UTC
started
Aug 17, 2026, 20:40 UTC
resolved
6h 6m
duration
Major
impact

Affected components

  • Automations
  • Cloud Agents
  • Origin
  • Review Agents
  1. resolvedAug 17, 2026, 20:40 UTC

    The affected Cursor services have recovered. We’re resolving this incident and will continue monitoring service health.

  2. investigatingAug 17, 2026, 19:43 UTC

    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/)

  3. investigatingAug 17, 2026, 15:25 UTC

    We are currently investigating this issue. We will provide updates as more information becomes available.

  4. investigatingAug 17, 2026, 14:34 UTC

    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/

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

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

Cursor outage on Aug 17, 2026: GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase · APIStatus.watch