Grok
Operational
03:38:52 UTC
No public incident
Official ↗Operational
03:38:52 UTC
No public incident
Official ↗This tool's status record
Only official snapshots saved by this site are counted. Uncollected periods stay blank.
Resolved official incidents
Grok · Resolved · Official component match
Grok · Resolved · Official title mentions tool
Grok · Resolved · Official component match
Grok · Resolved · Official component match
Grok · Resolved · Official component match
Grok · Resolved · Official component match
Grok · Resolved · Official component match
Related official component
Cursor Grok Bot is a separate Cursor status component. Check Cursor IDE, CLI, and Cloud Agents.
Or is it your account/network?
Official status only answers whether the service is failing. These checks keep quota and local issues separate.
Read this card's component lights and official incident. If amber or red, follow the incident and wait for recovery.
If status is green but requests fail, check Usage, HTTP 429 rate limits, and HTTP 529 capacity.
HTTP 429 · HTTP 529Sign in again, then check system time, network, regional restrictions, organization policy, and IDE extension version.
View incident detailsOther tools
Operational
00:04:59 UTC
No public incident
Official ↗Degraded
03:38:48 UTC
Operational
20:01:40 UTC
No public incident
Official ↗Operational
00:04:37 UTC
No public incident
Official ↗Could not read official status. Unknown is not operational.
FAQ
Read active public incidents from xAI official RSS and their affected Grok.com, Voice, Imagine, iOS, Android, or Grok in X surfaces.
Not necessarily. The official RSS reports product surfaces and may not name a specific model version. This site does not claim a model version is affected unless the official event says so.
No. Grok Bot is a Cursor component disclosed on Cursor official status and remains on the Cursor page.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
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.