Major impactResolvedAI/ML

Cursor outage: Investigating service degradation - xAI models

Cursor reported this major-impact incident on its official status page on Sep 29, 2026, 19:43 UTC. It was resolved after 35 min.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 29, 2026, 19:43 UTC
started
Sep 29, 2026, 20:18 UTC
resolved
35 min
duration
Major
impact

Affected components

  • CLI
  • Cloud Agents
  • Grok Bot
  • IDE

Timeline

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

    This incident has been resolved.

  2. identifiedSep 29, 2026, 20:01 UTC

    We have identified the cause of degraded performance affecting xAI models and are working to restore full capacity. Users may see errors, slow responses, or rate limiting on these models, and some Cloud Agent tasks may fail. We will post another update shortly.

  3. investigatingSep 29, 2026, 19:43 UTC

    We are investigating a service degradation affecting xAI models. Some Agent requests may fail.

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 service degradation — Cloud Agents and Grok Bot (Sep 29, 2026)Next: Investigating service degradation — Grok Bot and Review Agents (Oct 3, 2026) →
Cursor outage on Sep 29, 2026: Investigating service degradation - xAI models · APIStatus.watch