Minor impactResolvedAI/ML

Cursor incident: Investigating service degradation - Grok 4.7

Cursor reported this minor-impact incident on its official status page on Sep 23, 2026, 20:28 UTC. It was resolved after 9 min.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 23, 2026, 20:28 UTC
started
Sep 23, 2026, 20:36 UTC
resolved
9 min
duration
Minor
impact

Affected components

  • Automations
  • CLI
  • Cloud Agents
  • IDE

Timeline

updates from Cursor's status page ↗
  1. resolvedSep 23, 2026, 20:36 UTC

    This incident has been resolved.

  2. monitoringSep 23, 2026, 20:31 UTC

    A fix has been implemented and we are monitoring for service restoration.

  3. investigatingSep 23, 2026, 20:28 UTC

    We are investigating degraded performance for requests that use Grok 4.7.

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

← Previous: Investigating — Cloud Agent Dockerfile Builds (Sep 23, 2026)Next: Investigating service degradation — Grok Bot (Sep 25, 2026) →
Cursor incident on Sep 23, 2026: Investigating service degradation - Grok 4.7 · APIStatus.watch