On this page
The Cursor status page and status API reported issues with Composer 2.5 requests on the evening of 2026-11-05 Asia/Shanghai. Incident id ps_78783e1b35b98b43, titled composer-2.5 degraded, carries impact minor. The investigating notice went up at 23:06:52 Asia/Shanghai; a resolved update followed at 23:56:32 Asia/Shanghai—49 minutes and 40 seconds later, or about 50 minutes in plain terms. We haven't tested Composer 2.5 requests, and we have not reproduced failures on the IDE, CLI, Cloud Agents, or the other components named below. Everything below is a status-page / status-API self-report, not a live product test.
Related DigIntoAI notes: Cursor Pricing (October 2026), How Cursor Usage Limits Work on The X Subscription and Legacy Plans (October 2026), Cursor Cloud Agents: Interactive Canvas, Environments API, and Cursor Remote Control: Run Local Agents From Your iPhone.
What Cursor reported
At 2026-11-05 23:06:52 Asia/Shanghai (2026-11-05T15:06:52Z), the incident opened in investigating with this wording: We are currently experiencing issues with Composer 2.5 requests.
The public record has no identified or monitoring update between those two poles. At 23:56:32 Asia/Shanghai (2026-11-05T15:56:32Z), the status API moved the incident to resolved, and resolved_at is set to that same timestamp. The resolved update is one sentence: This issue has been resolved. The status API does not name a root cause, a fix, or extra detail on how Composer 2.5 requests failed.
A DigIntoAI re-check on 2026-11-06 ~00:06 Asia/Shanghai still shows the incident resolved, the overview All Systems Operational, indicator none, all 11 components operational, and no open incidents.
Scope: Composer 2.5 requests
The incident name and the investigating update both point at Composer 2.5 requests. Impact is listed as minor on the status API record. The filing does not describe every Cursor component as failed.
While the incident was still in investigating, a snapshot around 23:55 Asia/Shanghai showed the overview as Partially Degraded Service with indicator minor. Six components showed degraded performance:
- IDE
- Cursor IDE (iOS)
- CLI
- Cloud Agents
- Automations
- Bugbot
Five other components on the same summary stayed operational at that time: cursor.com, Grok Bot, Third-party models, Origin, and Enterprise Dashboard. Grok Bot remaining operational is part of this incident's own snapshot—the Composer 2.5 request issue and Grok Bot's green status sat on the same status page at the same time.
Resolved after about 50 minutes
From 23:06:52 to 23:56:32 Asia/Shanghai, the public ticket ran for 49 minutes and 40 seconds. That is about 50 minutes, not a rounded-up hour. The official close is only the resolved sentence above; that line is not a published root-cause analysis.
After the close, status.json and summary.json on 2026-11-06 ~00:06 Asia/Shanghai show All Systems Operational / indicator none. All 11 components on the summary—including the six that had shown degraded performance—are listed as operational, and the open-incident list is empty. page.updated_at at that check was 2026-11-05T16:06:15Z (2026-11-06 00:06:15 Asia/Shanghai), a page refresh after the incident's resolved_at, not a second progress note.
Timeline (Asia/Shanghai, with UTC)
| Clock (Asia/Shanghai) | UTC | Status API step |
|---|---|---|
| 2026-11-05 23:06:52 | 2026-11-05T15:06:52Z | investigating — issues with Composer 2.5 requests |
| Snapshot ~23:55 | — | Overview Partially Degraded Service / minor; six components degraded; cursor.com, Grok Bot, Third-party models, Origin, and Enterprise Dashboard operational |
| 2026-11-05 23:56:32 | 2026-11-05T15:56:32Z | resolved — This issue has been resolved; no root cause |
| Check ~00:06 (Nov 6) | 2026-11-05T16:06:15Z | Still resolved; overview All Systems Operational; 11 components operational; open incidents = 0 |
DigIntoAI status
We haven't tested Composer 2.5 requests for this incident, and we have not reproduced failures on the IDE, Cursor IDE (iOS), CLI, Cloud Agents, Automations, or Bugbot. The notes follow the Cursor status page and status API self-report only. Product status can change afterward; the Cursor status page and status API take precedence.
Quick facts
- Source. Cursor status page + status API (
status.json/summary.json/incidents.json). - Incident.
ps_78783e1b35b98b43— composer-2.5 degraded. - Impact. minor.
- Opened. 2026-11-05 23:06:52 Asia/Shanghai (investigating): We are currently experiencing issues with Composer 2.5 requests.
- Resolved. 23:56:32 Asia/Shanghai (
resolved_at＝2026-11-05T15:56:32Z): This issue has been resolved. Duration about 50 minutes. No root cause in the update. - During the incident. Overview Partially Degraded Service; degraded: IDE, Cursor IDE (iOS), CLI, Cloud Agents, Automations, Bugbot. Still operational: cursor.com, Grok Bot, Third-party models, Origin, Enterprise Dashboard.
- Later check (~00:06 Nov 6). Overview All Systems Operational / indicator none; 11 components operational; open incidents = 0.
- Live test. Status self-report only; no live Composer 2.5 request test.
- Related. Cursor pricing, usage limits, Cloud Agents canvas / Environments API, remote control from iOS.
In short
The Cursor status API shows a minor incident for Composer 2.5 request issues, opened 2026-11-05 23:06:52 Asia/Shanghai and resolved at 23:56:32—about 50 minutes later—with only the close line This issue has been resolved and no root cause. During the investigating window the overview was Partially Degraded Service, six components showed degraded performance, and Grok Bot plus four other components stayed operational. A later check still shows All Systems Operational. We haven't tested Composer 2.5 requests; the notes follow the Cursor status page and status API only.