Partial outageCursorJune 16, 2026

Elevated errors across many models on Anthropic

A record of the Cursor incident on June 16, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.

Started
Jun 16, 2026, 06:00 PM UTC
Resolved
Jun 16, 2026, 07:41 PM UTC
Duration
1h 41m
Impact
Partial outage

Other providers down at the same time

2 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.

Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.

How big was this outage?

This outage lasted 101 minutes. Across 36 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 15th longest.

Longer than a typical outage.

Only incidents recorded as major-or-worse and already resolved are counted.

Current status

Cursor is operating normally now. This incident has been resolved.

See current Cursor status

What you can do during an outage

Source: Cursor's official status page.

Other Cursor incidents

  1. Investigating service degradation — Cloud Agents and AutomationsSeptember 17, 2026
  2. Investigating service degradation — Grok BotSeptember 17, 2026
  3. Investigating service degradation — Grok BotSeptember 16, 2026
  4. Investigating service degradationSeptember 16, 2026
  5. Investigating service degradationSeptember 15, 2026