'Resolved,' Says SpaceXSI. A Surge of Grok Bot Users Say It Isn't, and Support Isn't Helping

SpaceXSI's status page says the problem that sent Grok Bot usage meters soaring overnight is over. Early Sunday, it posted five words: "This incident has been resolved." A surge of paying users say their meters never came back down, and that the support desk they were sent to has not helped.

Update, Nov. 1. Elon Musk gave the reason Sunday afternoon. Asked on X whether there was "any chance for a Grok Bot reset" because "lots of people say their usage ran out really fast this week," Musk replied: "The cost of serving Grok Bot was unsustainably high relative to revenue." His answer points to a deliberate decision tied to the cost of running Grok Bot, not a counting glitch.

The trouble started early Sunday. Users reported that the weekly usage meter for Grok Bot, SpaceXSI's SI agent, had doubled overnight or jumped straight to the 100% cap, locking them out for the rest of the week. Many said nothing was running.

Just over an hour after the first report in Cursor's forum bug thread, the status page opened an incident: "We are investigating a service degradation affecting our billing and usage dashboard." Five hours and 15 minutes later came the resolved notice. As of Sunday afternoon, the incident had not been reopened and no new one had been posted.

"Marked resolved, but meter not corrected"

The pushback started within half an hour of the notice.

In the forum, about 40 minutes after the notice, one user asked: "it’s said resolved but i’m still at 100%, how about you guys." Another wrote, "This incident is not fixed. Reopen and fix it." A third: "It’s for sure not fixed at all, this is an active bug/issue! Please fix it!"

More than eight hours after the notice, users were still posting the same thing.

Most of the forum thread came after "resolved": 48 of 75 user posts, from 36 people, 28 of whom had not posted there before. Not every one of those posts says the writer is still stuck. Many describe the original jump.

Cursor's own forum staff backed users up. About five hours after the notice, a staff member who posts as deanrie listed among the problems he had passed to the team "the fact that the values are still inflated even though the incident on status.x.ai is already marked as resolved." Later, he flagged a user whose other meters reset after a plan upgrade "but the weekly Grok Bot counter did not."

"A sharp jump in weekly Grok Bot usage without matching activity shouldn't happen, and it isn't related to your settings or routines," he wrote. He said he would not guess at a cause before the team replied. Before Musk's post, neither SpaceXSI nor Cursor had announced a cause, and neither had announced a reset of the extra usage as of Sunday afternoon.

How it hit

In the forum, a legacy Cursor Ultra subscriber said the meter read 53% and, about two minutes later, 100%. "At that same moment, Grok Bot's own usage check still said 53.7%," the subscriber wrote. A legacy SuperGrok Heavy customer who pays $300 a month said the meter went from 60% to 100% "in about 2 hours" while nothing was running.

Some of them run businesses on it. "I have a client presentation tomorrow and am now nearly blocked," wrote one Ultra subscriber. "Grok Bot is business critical to me as I run everything for my business on Grok Bot," wrote a SuperGrok Heavy customer on Finnish time, whose own usage report put Sunday at under 1% of the week's use.

What the numbers show

The forum thread offers a sample: 33 posters there gave both a before and an after reading, a small slice of everyone complaining on the forum and on X. Twenty-one were pinned at 100%. Of the other 12, 11 landed within 12% of exactly double where they started: 33% to 66%, 44% to 88%, 46% to 92%.

Users who track their own spending found the same thing. One who logs usage in Grafana said the weekly allowance looked cut in half, "from around $260 to $130." Another posted numbers from a usage export: 1,418 million tokens used 84.4% of the limit the week before, while 413 million tokens had already used 51.1% this week.

One user said the meter kept running hot after the jump. "Since the morning, the meter has been climbing about 4× faster per dollar than earlier in the week. So it's not just a one-time doubling; it's still over-counting," that user wrote. By the export, the meter should have read about 42%, not 96%.

The staff member said the thread showed Ultra, Pro+, legacy Pro and legacy SuperGrok Heavy plans were all affected. He said he would not guess at a cause before the team replied.

What users were told to do

The official guidance comes down to two steps. Cursor's forum staff told users with on-demand usage turned on to set a spending limit "so the inflated counter doesn't roll into paid usage," following Cursor's help page. That keeps the bug from billing more money. It does not give back the lost week. For that, the staff member said, a recalculation "can only be handled through support@x.ai."

Why users say it isn't working

Users say that road runs into Sam, the support desk's automated assistant. One wrote that Sam suggested "background routines are responsible." Another said the email replies kept saying the meter would reset "in 2 days like my meter says."

One user who spent Sunday emailing wrote: "After 7 hours of emails with him he asks me if i would like a human to look at the ticket." That user said Sam then put a human review "3 or 4 days" out. Another user's ticket was escalated to a human specialist "in 4 days though." Others said they filed tickets and got nowhere: "i have raised support ticket too… but no solution."

A three-to-four-day wait lands about when many weekly meters reset on their own anyway. One user on X said support told them "they can’t restore the lost usage or reset early."

Users who pushed through shared what got them furthest: one ticket, not several, since the staff member said duplicates will not speed things up; the usage CSV export; the before and after percentages and the time of the jump; and a direct request for a human. Even then, they report, the wait is days.