Cursor · 73d ago

Investigating Composer degradation

Resolved

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

Timeline

Started: 7/29/2026, 8:51:00 AM

Last update: 7/29/2026, 11:38:18 AM

Resolved: 7/29/2026, 11:38:18 AM

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

resolved
This incident has been resolved.
7/29/2026, 11:38:18 AM
investigating
We are continuing to investigate this issue and will provide updates as more information becomes available.
7/29/2026, 9:57:38 AM
investigating
We have resolved the service degradation with Grok 4.5 and are still investigating the degradation with Composer 2.5.
7/29/2026, 9:11:02 AM
investigating
We are investigating a service degradation with Grok 4.5 and Composer 2.5
7/29/2026, 8:51:54 AM