Investigating Service Degradation with VS Code Extensions
Cursor · Last saved provider status: investigating
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- investigating
- Provider impact
- minor
- Provider record created
- 29 Oct 2026, 21:38:10 UTC
- Provider record updated
- 29 Oct 2026, 21:38:10 UTC
- Explicit provider start
- 29 Oct 2026, 21:38:10 UTC
- Explicit provider end
- Not available
Affected components reported by the provider
- IDE
rflc60xp5jp2
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
The eleven reviewed Cursor components and the incident and maintenance lists supplied by its official compatibility report. Grok and xAI API components are excluded. This does not independently test any model, account or region.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- investigating
We are investigating a service degradation with VS Code extensions
Seen in a saved revision at 29 Oct 2026, 21:39:31 UTC