Investigating service degradation , Automations and Cloud Agents w/ Grok 4.7
Sep 22, 13:02 UTCSep 22, 13:45 UTC
Duration
44m
Impact
Minor
Root cause
Not disclosed
Cursor, 90 days
82 incidents
Affected
AutomationsCloud Agents
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 22, 13:45 UTC
This incident has been resolved.
- Identified · Sep 22, 13:08 UTC
The root cause has been identified and a fix is being implemented.
- Investigating · Sep 22, 13:02 UTC
We are aware of an issue where Grok 4.7 fails to be selected as a model for Cloud Agents. We are investigating the issue.
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 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 |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.