Cursor incident

Investigating Grok 4.5 degradation

Resolved after 2 hours 35 minutes, affecting Automations and Review Agents and 1 more, on July 16, 2026.

monitoring Jul 16, 2026, 09:34 AM UTC

A fix has been implemented and we are monitoring for service restoration.

Started
Jul 16, 2026, 07:01 AM UTC
Resolved
Jul 16, 2026, 09:36 AM UTC
Duration
2h 35m
Detected by Pingoru
Jul 16, 2026, 07:01 AM UTC

Affected components

AutomationsReview AgentsCLICloud Agentscursor.comIDE

Update timeline

  1. investigating Jul 16, 2026, 07:01 AM UTC

    We are investigating partial degradation of Grok 4.5. Users should switch to Auto or try another model.

  2. investigating Jul 16, 2026, 07:22 AM UTC

    We are continuing to investigate this issue. We will provide updates as more information becomes available.

  3. investigating Jul 16, 2026, 07:35 AM UTC

    We are continuing to work on the Grok 4.5 degradation. Please switch to Auto or try another model.

  4. investigating Jul 16, 2026, 07:50 AM UTC

    Investigation is ongoing for degradation of Grok 4.5. Users should switch to Auto or try another model while we work toward a resolution.

  5. monitoring Jul 16, 2026, 09:34 AM UTC

    A fix has been implemented and we are monitoring for service restoration.

  6. resolved Jul 16, 2026, 09:36 AM UTC

    This incident has been resolved.

Your product runs on more than Cursor

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →