Moonshot AI's Kimi account apologized on October 25, 2026 (PST) for rate limits and unnecessary quota consumption that subscribers hit while using K3.1 Pro. The company said the faults were its own and that it should have fixed them sooner. It promised a one-time usage reset for every active subscription plan, restoring 25% of monthly quota (about one week of usage), with the usage bar updated by end of that PST day.
Key Facts
| Details | |
|---|---|
| Who | Kimi / Moonshot AI (@Kimi_Moonshot) |
| When | October 25, 2026 (PST); Chinese media reported the same statement early October 26 UTC+8 |
| Product affected | K3.1 Pro on paid subscription plans |
| Problems admitted | Rate limiting; unnecessary quota consumption |
| Compensation | One-time reset for all active plan tiers: restore 25% of monthly quota; if current usage is under 25%, reset usage to 0 |
| UI timing | Usage bar to show the adjustment by end of day PST on the apology date |
| Follow-up change | Adjusted plan parameters; reducing unnecessary subagent calls and output length |
| Prior release | K3.1 Pro launched about October 24, 2026 (per IT之家 and PANews) |
Background
K3.1 Pro is the first model in Moonshot's Kimi K3.1 line. IT之家 and PANews both place the launch on October 24, 2026. Within about a day, paying members reported throttling and faster-than-expected quota burn while using that model.
The English statement on X, as quoted by Digg, matches the Chinese apology letter reprinted in full by IT之家: Moonshot takes responsibility, offers the 25% reset across every active tier, and says it is already changing configuration so the same quota completes more real work.
What We Don't Know Yet
- Root-cause detail beyond "rate limits and unnecessary quota consumption" (no public postmortem yet).
- Whether rate-limit ceilings themselves changed, or only quota accounting and subagent/output settings.
- How many subscribers were affected, and how much unused quota was restored in aggregate.
- Parameter counts and other model-card claims for K3.1 Pro beyond the launch date (not independently re-verified for this story).