Degraded performance for Grok Bot routine triggers
Sep 3, 23:42 UTCSep 4, 00:42 UTC
Duration
1h
Impact
Major
Root cause
Not disclosed
Cursor, 90 days
82 incidents
Affected
Grok Bot
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 4, 00:42 UTC
This incident has been resolved.
- Identified · Sep 4, 00:13 UTC
The root cause has been identified and a fix is being implemented.
- Investigating · Sep 3, 23:42 UTC
We are investigating a service degradation affecting Grok Bot. Some trigger fires may be dropped.
More from Cursor
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2320:28 UTC | Investigating service degradation - Grok 4.7 | minor | 9m |
| Sep 2317:14 UTC | Investigating , Cloud Agent Dockerfile Builds | minor | 1h 29m |
| Sep 2213:02 UTC | Investigating service degradation , Automations and Cloud Agents w/ Grok 4.7 | minor | 44m |
| Sep 2201:07 UTC | Investigating service degradation | minor | 36m |
| Sep 2106:39 UTC | Investigating service degradation | minor | 22m |
| Sep 1823:02 UTC | Sign-in and dashboard errors for some users | minor | 11m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.