Skip to main content

Cursor · 89d ago

Investigating Grok 4.5 degradation

Resolved

Yes — Cursor had a problem on July 16, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”

See Cursor's live status →

Timeline

Started: 7/16/2026, 7:01:00 AM

Last update: 7/16/2026, 9:36:45 AM

Resolved: 7/16/2026, 9:36:45 AM

Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2

Cursor's official report →

Updates

  • resolved

    This incident has been resolved.

    7/16/2026, 9:36:45 AM

  • monitoring

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

    7/16/2026, 9:34:06 AM

  • investigating

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

    7/16/2026, 7:50:05 AM

  • investigating

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

    7/16/2026, 7:35:31 AM

  • investigating

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

    7/16/2026, 7:22:10 AM

  • investigating

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

    7/16/2026, 7:01:29 AM

More Cursor incidents

Is Cursor down right now?All outage history →

Is Cursor down? Cursor is up now — Jul 16, 2026 outage | AI Status