Degraded performance of Grok 4.6
Aug 25, 14:54 UTCAug 25, 17:36 UTC
Duration
2h 43m
Impact
Minor
Root cause
Not disclosed
Cursor, 90 days
82 incidents
Affected
CLICloud AgentsIDEGrok Bot
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 25, 17:36 UTC
This incident has been resolved.
- Monitoring · Aug 25, 16:20 UTC
We are seeing signs of improvement and will continue to monitor for service restoration.
- Identified · Aug 25, 15:29 UTC
The root cause has been identified and a fix is being implemented.
- Investigating · Aug 25, 14:54 UTC
We are investigating a service degradation affecting Grok 4.6.
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.