The Cutoff ReportSearch

Cursor degradation — 2026-08-11

Partially Degraded Service It began at 2026-08-11 17:30 UTC and is still ongoing after 55 min. We recorded 20 failing checks during the window.

Check-by-check timeline

  • 2026-08-11 17:18 UTCOperational239ms · HTTP 200All Systems Operational
  • 2026-08-11 17:21 UTCOperational244ms · HTTP 200All Systems Operational
  • 2026-08-11 17:24 UTCOperational241ms · HTTP 200All Systems Operational
  • 2026-08-11 17:27 UTCDegraded632ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:30 UTCDegraded331ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:33 UTCDegraded244ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:36 UTCDegraded361ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:39 UTCDegraded279ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:42 UTCDegraded369ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:45 UTCDegraded150ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:48 UTCDegraded316ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:51 UTCDegraded293ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:54 UTCDegraded423ms · HTTP 200Partially Degraded Service
  • 2026-08-11 17:57 UTCDegraded403ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:00 UTCDegraded160ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:03 UTCDegraded335ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:06 UTCDegraded303ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:09 UTCDegraded256ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:12 UTCDegraded371ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:15 UTCDegraded813ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:18 UTCDegraded244ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:21 UTCDegraded286ms · HTTP 200Partially Degraded Service
  • 2026-08-11 18:24 UTCDegraded261ms · HTTP 200Partially Degraded Service

Current Cursor status and full outage history

How this is measured

Readings are taken every few minutes from outside Cursor's network, combining their published status feed with a timed request to the service itself.

An incident opens after two consecutive bad readings and closes after two consecutive good ones, so the recorded duration may be a few minutes wider than the true outage.

Cursor's official status page is the authority on causes and affected components.