Cursor Status · History · Incident #7027
RESOLVEDGrok Bot computers unreachable for some users
Major · Started Sep 7, 2026 · 8:32 PM
Cursor Status · History · Incident #7027
RESOLVEDMajor · Started Sep 7, 2026 · 8:32 PM
Duration
1h 5m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Sep 7, 2026 · 8:32 PM
Resolved
Sep 7, 2026 · 9:37 PM
Duration
1h 5m
Severity
Major
Event timeline
Investigating
Sep 7 · 8:32 PM CursorWe have identified an issue affecting Grok Bot. Some users may be unable to reach their Grok Bot computer, and Recover or Reset may fail. Your data is not affected. A fix is rolling out and we will post another update shortly.
Identified
Sep 7 · 8:33 PM CursorThe root cause has been identified and a fix is being implemented.
Monitoring
Sep 7 · 8:41 PM CursorA fix has been implemented and we are monitoring for service restoration.
Resolved
Sep 7 · 9:37 PM CursorThis incident has been resolved.
Pattern
Investigating service degradation — Review Agents and Cloud Agents
Sep 10, 2026 · 24m
View incident →Investigating service degradation — CLI, Cloud Agents, and IDE
Sep 7, 2026 · < 1m
View incident →Degraded performance for Grok Bot routine triggers
Sep 3, 2026 · 59m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.