What to do if your meter jumped
Compare the meter with your own work
Open Usage at grok.com/dashboard and note the percentage, the time it jumped and the next reset date. A Cursor staff member said on Cursor's forum that a sharp jump in weekly Grok Bot usage without matching activity shouldn't happen and isn't related to your settings or routines.
Check xAI's status page
status.x.ai lists incidents for Grok, Grok Bot and the billing and usage dashboard. If an incident is open, wait for it to resolve before you buy more usage.
Cap paid usage while it's sorted out
Cursor's staff advised setting a spending limit so an inflated counter doesn't roll into paid usage. On The X Subscription, leave Auto Top-up off or set a Monthly additional usage limit on the billing page; on a legacy Cursor plan, set the On-demand monthly limit.
Ask support for a recalculation
Cursor's staff said questions about a specific account, including usage recalculation, are handled at support@x.ai, and one open ticket is enough. Include the time of the jump and a screenshot of the meter.
Keep coding work moving
Open Reason on the web at reasonmachines.com, or in the Reason app for Mac, sign in and connect GitHub. Choose the repository and describe the task, for example "fix the failing tests". The session works in your repository on Reason's own cloud computer, runs the tests and opens a pull request, and it uses your Reason plan's credits, not your Grok weekly pool, so it keeps going whether or not Grok Bot has usage left. With Reason connected to Grok Bot, Grok Bot can also start a session for you; its own messages, including that one, still count toward the weekly pool.
Timeline: November 1, 2026
| Time (UTC) | What happened | Source |
|---|---|---|
| About 04:10 to 04:20 | The spike time Cursor's staff later passed to the team for the jump in weekly Grok Bot usage. | Cursor forum, staff reply |
| 04:25 | A user on Cursor Ultra reports the weekly meter "keeps flipping in real time: 74%, then 77%, then 100% (capped), back to 77%, back to 100%, over and over", starting around 12:18 AM ET, while their own tracking read about 77.7%. | Cursor forum, bug report |
| 05:39 | status.x.ai opens "Service Degradation - Billing and Usage Dashboard": "We are investigating a service degradation affecting our billing and usage dashboard." It lists cursor.com and the Enterprise Dashboard as affected. | status.x.ai, via an independent status tracker |
| 14:36 | A user on a legacy SuperGrok Heavy plan reports usage "jumped from 60% to 100% in about 2 hours" with nothing running, and that Bots "now fail with “Reached usage limit.”" | Cursor forum |
| 16:05 | Cursor's staff reply that the values "are still inflated even though the incident on status.x.ai is already marked as resolved" and pass the details to the team. | Cursor forum, staff reply |
| 20:34 | Elon Musk, replying to @DogecoinNorway: "The cost of serving Grok Bot was unsustainably high relative to revenue". | X |
| 21:37 | Elon Musk, replying to @dvorahfr: "Upgrade to higher usage plan cost increase is too high?" | X |
What xAI, Cursor and X have said
Elon Musk's replies are the only public word from xAI's leadership we found. They talk about serving cost and plan prices; they don't announce new limits or say the meter readings were correct.
Cursor's forum staff, who handle Grok Bot support there, said: "A sharp jump in weekly Grok Bot usage without matching activity shouldn’t happen, and it isn’t related to your settings or routines." They flagged the mismatch between what the Bot itself reports and what Settings and the app show.
X's trending story "Grok Bot Users Hit Sudden 100% Usage Limits Amid Cost Surge" says "A brief billing dashboard glitch caused some false readings, now resolved." X writes those summaries with Grok and labels them as possibly mistaken; we found no statement from xAI or Cursor in those words.
Display glitch or a real change?
The record supports both readings, and they aren't exclusive. The status incident and the staff reply point to inflated readings around 04:10 to 04:20 UTC. Musk's replies point to cost pressure on Grok Bot. As of November 1, 2026, xAI's usage-limits page was last updated on October 11, 2026, and still describes one weekly pool per paid seat with no new numbers.
Until xAI says more, plan for a tighter pool: keep paid usage capped, and move heavy coding work to a Reason session or your own coding agent so a Grok Bot limit doesn't stop it.
Sources
- Elon Musk on X: "The cost of serving Grok Bot was unsustainably high relative to revenue"
- Elon Musk on X: "Upgrade to higher usage plan cost increase is too high?"
- Cursor forum: Grok Bot weekly usage meter flips between 77% and 100% in real time
- Cursor forum: staff reply
- Cursor forum: usage jumped from 60% to 100%
- status.x.ai: Service Degradation - Billing and Usage Dashboard
- X trending: Grok Bot Users Hit Sudden 100% Usage Limits Amid Cost Surge
- xAI: Usage limits
Questions
Why did my Grok Bot usage jump to 100%?
On November 1, 2026, many users saw the weekly meter jump to 100% with no matching work, during a status.x.ai incident on the billing and usage dashboard. Cursor's staff said such a jump shouldn't happen and passed the reports to the team. If yours doesn't match your work, ask support@x.ai for a recalculation.
Was the Grok Bot usage spike a bug?
The readings were at least partly wrong: xAI's status page reported a billing and usage dashboard degradation, and Cursor's staff said values stayed inflated after it was marked resolved. Separately, Elon Musk said serving Grok Bot cost too much relative to revenue. Neither has said whether limits changed.
Why is Grok bot usage stuck at 100%?
Because your seat's weekly pool is used up: the meter stays at 100% until the reset date in your usage view, unless you buy a top-up for paid Additional Usage or move to a bigger plan. Over Halloween weekend (October 31 to November 1, 2026), some users' meters jumped to 100% without overnight use; TechCrunch and Business Insider reported on November 2 that Elon Musk replied "The cost of serving Grok Bot was unsustainably high relative to revenue", and TechCrunch says he confirmed it was not a glitch.
Why does my Grok Bot usage meter flip between 77% and 100%?
Users on Cursor's forum reported it from November 1, 2026: the weekly meter in the Grok Bot app flipped between about 77% and 100% while their own usage checks still read about 77%. xAI's docs don't explain the flip. Go by the usage view at grok.com/dashboard, and if it doesn't match your work, contact support@x.ai with the times you saw each reading.
Did Grok Bot's usage limits change?
xAI hasn't published new pool sizes. Its usage-limits page, last updated October 11, 2026, still describes one weekly pool per paid seat shared across Grok and Cursor surfaces.
Will my usage be reset?
Cursor's staff said account questions, including usage recalculation, are handled at support@x.ai. Otherwise your pool comes back on the reset date in your usage view.
Does handing work to Reason stop Grok Bot from using my weekly pool?
No. Grok Bot's own messages, including the one where it starts a Reason session, still draw from your Grok weekly pool. The coding work itself (reading the code, running builds and tests, opening the pull request) runs in the Reason session on Reason's cloud machine and uses your Reason plan's credits instead.
Is Reason made by xAI?
No. Grok Bot is a product of xAI. Reason is built by Reason Machines and is not affiliated with or endorsed by xAI. Limits and prices on this page come from xAI's own documentation; check it for changes.
More guides
- Grok Bot usage limit
- Grok Bot limit reached
- Grok Bot weekly limit
- Grok Bot alternatives
- Grok Bot usage limit changes
- How to keep using Grok Bot after the limit
- Grok Bot for coding: can Grok Bot code?
- Grok Bot vs Claude Code
- Grok Bot vs Codex
- Grok Bot vs Claude Code vs Codex
- Grok Bot vs Devin
- How to use Grok Bot with Claude Code
- Reason for Grok Bot: a software engineer for your Bot
- Reason Network: Grok Bot messages your own Claude Code or Codex