Cursor
Cursor
No data
Last success —
No component payload
Delayed responses in Grok Bot
4 up1 degraded0 down1 unknown
Snapshot 03:38:52 UTC
updates every 60s
Official incident · Cursor
Delayed responses in Grok Bot
resolved · 2026-10-27 20:33:09 UTC · Resolved 2026-10-27 20:43:04 UTC
Duration 9mOfficial component matchmajorGrok Bot
Official updates
- resolved
This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.
- investigating
We're investigating an issue causing delayed responses in Grok Bot. We'll share an update as soon as we have more information.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
- status.claude.com/api/v2/summary.json
- status.openai.com/api/v2/summary.json + components.json
- status.x.ai/api/compat/summary.json (Cursor)
- status.x.ai/feed.xml (Grok)
- www.githubstatus.com/api/v2/summary.json
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.