Live  /  Cursor  /  Incident

Cursor: Investigating Service Degradation with VS Code Extensions

Cursor · cursor.comMinor incidentResolved2026-10-30 07:12 UTC
Public — what happened

Summary

Cursor reported a minor service degradation affecting VS Code extensions, and said it began investigating at 21:38 UTC on October 29, 2026. The company did not describe a cause or say which users were affected. At 07:12 UTC on October 30, Cursor said the incident was resolved and that all services were operating normally again.

Affected

IDE

As listed on Cursor’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cursor against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cursor: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Cursor report →

More from Cursor

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Cursor status & history page.

Related: Cursor status & history. SquidGrid is not affiliated with Cursor.