Claude Opus 4.5 multiplier already at 3x instead of 1x?

[Lennard00]

Select Topic Area

Question

Copilot Feature Area

General

Body

I seem to consume a significant higher amount of premium requests with Claude Opus 4.5 although the model should still be in its promotional period of having a multiplier of 1 (through Friday, December 5, 2025). The difference in request usage is quite obvious: my actual request consumption has been relatively stable over the days whereas my premium request usage has shot through the roof.

Does anyone else also recognize this?

Can we please get a look into this? And if suspicions are correct: a quick reset of the premium request usage?|

Thanks

[Rxyanlaw]

Can confirm as well

[Dinuka-Nonis]

I’m actually seeing the same thing. My normal usage hasn’t changed much at all, but the premium request counter suddenly started jumping way faster than it should! especially if Opus 4.5 is still in the 1× promo period. Something definitely feels off.

[ridge-rider]

Yup was getting this too ... suddenly x3 rate instead of x1

[pearuarmasj]

Yeah whatever happened to this BS? As the famous saying goes, "So that was a F'ing lie".

[dwmongoose]

Can confirm. This was slipped in on the sly. I didn't even realize I was burning 3x...just noticed that my percentage was going up fast and then bam 3x...wow.

[Afakhar27]

I’m seeing the same thing too : Opus 4.5 is suddenly being counted at 3× instead of the 1× promo rate, so it’d be great if the team could check whether something’s off.

[ridge-rider]

I noticed the indicator (in the image), but in the model options it was still showing x1 rate ... wondered if it was a bug but seems like not as it now also shows as x3 rate ... wtf?

[E5Anant]

I seem to consume a significant higher amount of premium requests with Claude Opus 4.5 although the model should still be in its promotional period of having a multiplier of 1 (through Friday, December 5, 2025). The difference in request usage is quite obvious: my actual request consumption has been relatively stable over the days whereas my premium request usage has shot through the roof.

Does anyone else also recognize this?

Can we please get a look into this? And if suspicions are correct: a quick reset of the premium request usage?|

Thanks

[jst4upiyush]

Just saw my quota being completely exhausted. Then realized that Claude Opus 4.5 is using 3X tokens.
Can we please look into this? a quick reset of the premium request usage?

[Lakshit-Gupta]

well, this was the silly mistake , shoot email to github regarding this matter, and see wht will happen ,

[pearuarmasj]

Ha. They have ignored me twice now, so. :)

[cubenex]

they changed it on purpose and wont change it back. Antigravity has opus 4.5 still for free

[Wladefant]

It is now confirmed 3x, allthough after refreshing it does not even show up in the model list. But before that it definitely was there as 3x

[fliozzi]

"Just yesterday I ran out of credits. I was doing great with Opus 4.5 because it was giving me excellent results, so I decided to upgrade from the Pro plan ($100 per year) to the Pro+ plan for $390 (4×). And of course, I was super happy about it. Today I wake up and see that Opus 4.5, my star model, is now at 3×. What a bummer — I barely got to enjoy it. Now I’m checking the plans and Opus 4.5 doesn’t even appear in the Pro plan anymore, only in Pro+. I don’t know what to do: downgrade back to Pro or stay on Pro+. I’m not a programmer, I just do this as a hobby, and $390 feels like a lot."
"I’m still thinking about it — whether to switch back to Pro or wait to see if Microsoft lowers it from 3× to 2× or less. Or maybe Google or OpenAI will release a better model. For now, GPT 5.1 Codex Max seems like an excellent alternative; it even surpasses Opus 4.5 in many aspects."

[dareios21]

claude opus 4.5 beats everything. i am so sad that went 3x. i am a bit of vibing with vscode. i am not a programmer. i am saying my thoughts to opus and just does what i want perfectly.

[dcomet90]

Hello team,
This issue, where the request multiplier for Claude Opus 4.5 jumped from the promotional 1x to 3x, is clearly a backend billing or configuration anomaly, but its impact points to a potential traffic surge that should be independently verified.

Service Monitoring & Alerting: The immediate detection of a sudden, drastic spike in "premium request usage" by users, while "actual request consumption" remained stable, suggests a successful billing configuration change (intended or accidental). From a network perspective, we need to confirm if our edge network monitoring (load balancers, WAFs, traffic flow logs) registered a corresponding 3x increase in API calls or if the change was purely internal to the consumption engine.

Latency Impact: A sudden increase in the perceived "cost" per request might drive a large number of users to switch models or reduce usage, potentially altering network traffic patterns. If the 3x multiplier was pushed out without appropriate capacity planning, it could signal an attempt to throttle usage that might indirectly introduce service latency if the underlying infrastructure is saturated.

Audit Trail: The core issue is an unannounced configuration change affecting user billing. We need to confirm that the internal change control logs align with the reported time of the multiplier change, ensuring that the appropriate security and financial audit trail is intact.

Recommendation: The GitHub team needs to Rollback the 3x multiplier immediately and communicate the root cause. Concurrently, a full traffic analysis should be executed to differentiate between a simple multiplier misconfiguration and a true service scaling anomaly caused by increased usage.

[codecanyon128]

This is very bad from GitHub. Has anyone tried Kilocode? It's ruining our $20 plan. How many requests do you give it?

[Dev-x777]

Yeah I'm noticing kinda similar thing on my side too. Usage was normal for a few days then suddenly premium counter just jumped like crazy even tho I didn't change how much I'm using it. I also thought promo period means 1x multiplier so idk why it's counting more.

Maybe some bug in tracking or reporting? Would be nice if the team can check logs and maybe rollback the extra usage if its wrong. Just wanted to add that you're not alone, seeing same behaviour here.

Hope it gets sorted soon!!!