At 12:18 in the morning Eastern time on 1 November, somebody on Cursor Ultra watched their Grok Bot usage meter do something meters are not supposed to do. In their words: "the weekly usage meter under Usage at the bottom of the Grok Bot app keeps flipping in real time: 74%, then 77%, then 100% (capped), back to 77%, back to 100%, over and over." By the next afternoon the thread had 140 posts and over two thousand views, and a lot of people's bots had stopped working for a weekend.

Most of it has since been put right, some of it has not, and nobody from Cursor has explained it in the thread. This post is what the meter counts according to Cursor's own pages, what happened on 1 and 2 November according to the people it happened to, and what to do if your meter does it again. Checked on 3 November 2026, and the thread again on 5 November, when it had 178 posts and still none from Cursor staff.

📈 What happened, in order

Night of 31 October to 1 November. Reports pile up within the hour: 33% to 66%, 45% to 92%, 34% to 73% "despite no user activity or scheduled routines running". Several people notice the bot and the settings screen disagree: "The bot indicates that my usage is at 24%, while the Settings page shows 48%." Bots that reach a false 100% stop working, and routines fail.

Morning of 1 November. People in the thread link an incident on xAI's status page, which answers scripts with a 403 so I could not read it myself, and a later post describes it as a "billing and usage dashboard incident". By late morning UTC the incident reads as resolved. The meters do not: "it's said resolved but i'm still at 100%, how about you guys".

2 November, about 08:00 UTC. Meters start coming back. "My weekly usage suddenly dropped from 80% back to 40% today, November 2, without a weekly reset, plan change, or any action on my part." Others confirm the same within the hour.

Still open. Two complaints did not go away with the fix. Some people were billed for on-demand usage while the false 100% was showing: "on-demand still shows $8.66 billed while the false 100% was showing. So the usage was corrected, but it wasn't just a visual artifact." And several people who track their own token counts say the rate itself changed. More on that below.