Cursor
Grok Bot
No data
Last success —
No component payload
Multiple services degraded
4 up1 degraded0 down0 unknown
Snapshot 03:20:39 UTC
updates every 60s
Official incident · Grok Bot
Multiple services degraded
resolved · 2026-10-28 21:15:10 UTC · Resolved 2026-10-28 23:13:34 UTC
Duration 1h 58mOfficial component matchmajorGrok Bot
Official updates
- resolved
This incident has been resolved. All services have returned to normal operation.
- investigating
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
- resolved
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
- investigating
A fix has been implemented and services are starting to recover. We will share another update shortly.
- investigating
We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.
- investigating
We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.
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.