Investigating service degradation - Grok 4.7
Sep 23, 20:28 UTCSep 23, 20:36 UTC
Duration
9m
Impact
Minor
Root cause
Not disclosed
Cursor, 90 days
82 incidents
Affected
AutomationsCLICloud AgentsIDE
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 23, 20:36 UTC
This incident has been resolved.
- Monitoring · Sep 23, 20:31 UTC
A fix has been implemented and we are monitoring for service restoration.
- Investigating · Sep 23, 20:28 UTC
We are investigating degraded performance for requests that use Grok 4.7.
More from Cursor
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| 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 |
| Sep 1817:19 UTC | Investigating service degradation , Grok Bot | major | 5h 43m |
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.