Fix problems
Is Grok Bot down? Live status, incidents and how to tell an outage from an account problem
By Tal Slavin · Last checked · Next review 2026-11-06
Is Grok Bot down? Live status, incidents and how to tell an outage from an account problem
Check Grok Bot status on status.x.ai, see where incident history lives, and tell a service-wide outage from a problem with only your account.
◈Key Takeaways (5)
- •Official status is at status.x.ai; the Grok Bot component covers Bots and their computer.
- •An open incident with many users affected is an outage; a green page with only your Bots failing points at your account or computer.
- •A green page is not proof: forum reports have led declared incidents by about three hours.
- •During an incident, wait for Resolved and resend; do not Reset or reinstall.
- •Failed messages and missed routine triggers were not replayed after past incidents.
☰On this page (6 sections)
Open status.x.ai and read the Grok Bot component. If an incident is open, wait for it to be marked resolved and then resend. If the page is green and only your Bots fail, the problem is your account, your computer, a waiting card or your usage, and you can work through the recovery order.
We could not read the live page on October 30 (it blocks automated requests), so this guide does not state today's status. It tells you where to look and how to read it.
Where to check#
| Where | What it shows |
|---|---|
| status.x.ai | Current state of Grok Bot and cursor.com |
| status.x.ai/history | Past incidents with start and resolve times, including Cursor's earlier history |
| status.x.ai/feed.xml | Declared incidents; add it to Slack with /feed subscribe |
Incident times on the page can be shown in UTC or your own time zone, so check the setting before comparing a window with your own failure.
Outage or account problem?#
| Sign | Likely cause |
|---|---|
| Open incident touching Grok Bot or Cloud Agents; many users report the same thing at once | Service-wide incident |
| Page green; every Bot on your account fails | Your shared computer is stuck or unreachable |
| Page green; one Bot always fails, others fine | A safety filter on that Bot's history; start a new Bot |
| Page green; replies stop at a usage meter of 100 percent | Usage limit; see usage limits |
| Signed in but sending fails with an authentication error | Computer needs an update; see sign-in errors |
A green page is not proof. On September 16 the first forum report of unresponsive Bots came about 17 minutes before staff replied, and the incident was declared later.
What to do during an incident#
- Wait until the incident is marked Resolved.
- Resend your message, using Resend on a failed one.
- Rerun any routine that should have fired; triggers during the window were not retried.
- Do not Reset the computer or reinstall the app. Neither fixes a service incident, and a Reset restores the last saved snapshot and can lose recent unsynced work.
Recent incidents#
Our dated, UTC table of Grok Bot incidents from September and October 2026 is in the original status guide, including the October 8 scheduler delays and the October 13 trigger outage (about 17:52 to 20:29 UTC). That table is a dated copy, not a live feed. Confirm any specific time on status.x.ai.
Frequently asked questions#
Where is the official Grok Bot status page?#
At status.x.ai. Cursor said its status updates would move there from October 26, 2026, and the older status.cursor.com addresses redirect to it. Watch the Grok Bot component for Bots and their computer and the cursor.com component for sign-in.
Should I reset the computer during an outage?#
No. A Reset does not fix a service incident, restores the last saved snapshot and can lose recent unsynced work. Wait for the incident to be marked resolved, then resend.
Are messages sent during an incident retried?#
Not automatically. After past incidents Cursor did not replay failed messages or missed routine triggers, so resend and rerun anything important by hand.
Is the status page always first to know?#
No. Forum reports have led declared incidents by about three hours, so a green page does not prove your account is fine.