Unexpected increase in my billing

[pcoganwu]

🏷️ Discussion Type

Question

Body

Unexpected GitHub Copilot Pro+ Charges – Has Anyone Experienced This?

Good afternoon everyone,

I'm hoping someone in the community may have experienced something similar or can help me understand what's happening with my GitHub billing.

I currently have a GitHub Copilot Pro+ subscription that expires in August 2026. My monthly charges have increased dramatically over the last few months:

• April 2026: USD $22.04
• May 2026: USD $237.14
• June 2026: USD $982.82

These increases were completely unexpected.

Some time ago, I accidentally subscribed to GitHub Pro, but I opened a support ticket and requested that it be cancelled. As far as I know, only my GitHub Copilot Pro+ subscription should still be active.

While reviewing my billing, I also noticed that my personal account is being charged USD $0.04 per unit. More recently, I started using GitHub Copilot Pro+ through my employer, and that account is billed at USD $0.01 per unit. This has left me wondering why the same service appears to have a fourfold difference in the per-unit rate.

Has anyone else experienced:

• A sudden increase in GitHub Copilot Pro+ charges?
• A billing rate of USD $0.04 per unit versus USD $0.01 per unit?
• Any insight into what these "per-unit" charges represent and why they might differ between accounts?

I've already contacted GitHub Support, but I wanted to ask the community if anyone has encountered something similar or has any suggestions on what I should check while waiting for their response.

Any advice or shared experiences would be greatly appreciated. Thank you!

[onur-g]

The unexpected surge in your June billing is a direct consequence of GitHub's transition from flat Premium Request Units to token-metered AI Credits, which took effect on June 1, 2026. Under the new model, usage is billed against input, output, and cached tokens at each model's published API rate, where one AI Credit equals $0.01 USD.

The vertical spike from April ($22.04) and May ($237.14) to nearly $1,000 in June typically happens when using autonomous agent modes, deep UIs, or looping chat sessions with heavy reasoning models. These workflows repeatedly re-send and re-process massive context windows with every turn, burning through credits at a rate that far outpaces the standard Pro+ monthly allowance.

The difference in per-unit rates—the $0.04 rate versus the $0.01 baseline—generally reflects an overage tier or markup applied once your included monthly credit allotment is exhausted, combined with differential model cost multipliers. Your employer account likely benefits from enterprise volume pricing, pooled organization credits, or subsidized corporate rate cards, shielding individual seats from the aggressive personal overage penalties. To verify the cause and mitigate further charges while awaiting support:

• Review your personal account's Usage tab to identify which specific models or agent loops triggered the token volume.
• Compact or reset chat threads frequently to prevent bloated context re-processing.
• Restrict heavyweight models to complex tasks and prefer lightweight defaults for routine queries.

[pcoganwu]

Thank you for the detailed explanation. I appreciate you taking the time to respond.

One thing that makes me question whether this is simply due to enterprise pricing is that my work account is not an Enterprise account—it's also a GitHub Copilot Pro+ subscription. The main difference I see is that my work account shows a rate of USD $0.01 per unit, while my personal account shows USD $0.04 per unit.

Also, I don't believe my usage justifies the June charges. I primarily use the ChatGPT 5.5 model and don't regularly use autonomous agents, long-running agent workflows, or deep research sessions that would consume a large volume of AI credits.

I'll review the Usage page as you suggested to see if there's anything unexpected, but I'm still trying to understand why there is such a large difference in the per-unit rate between the two accounts. If anyone else has seen a similar discrepancy between two non-Enterprise Copilot Pro+ accounts, I'd be interested to hear about your experience.

Thanks again for your suggestions.

[v-ember]

Hi @pcoganwu , thanks for posting in GitHub Discussions!

The Packages category is meant for questions about publishing, managing, and using packages hosted on GitHub. I've gone ahead and moved this post to our Copilot Conversations category, as this topic may be more relevant there and might help someone give you a nudge in the right direction. 😁

[AhmadHassan-BTed]

That's $0.04 versus $0.01 you just provided 😬 I think this happened.

When you opened that support ticket a while ago to cancel your accidental GitHub Pro subscription, it is highly likely that the support agent misunderstood and accidentally cancelled your Copilot Pro+ subscription instead, effectively downgrading your personal account to the standard Copilot Pro tier.

Copilot Pro ($10/mo): Charges $0.04 per unit for overages once you burn through its much smaller monthly allowance.
Copilot Pro+ ($39/mo): Charges $0.01 per unit for overages, and includes a massive base allowance (at least 4x more than standard Pro).

Because your personal account was likely downgraded by mistake, you lost your large Pro+ credit allowance. You hit the billing wall almost immediately, and every single prompt you sent to ChatGPT 5.5 was subsequently billed at the brutal 4x penalty rate of $0.04. That is exactly how your bill snowballed to nearly $1,000 without you even touching the heavy autonomous agents.

For what to do now?
Hurry and reply to your open Support ticket and explicitly point out the $0.04 per unit rate on your invoice. Tell them you strongly suspect a previous support agent accidentally downgraded your Copilot Pro+ subscription when you originally asked to cancel regular "GitHub Pro."

Once they check the logs and see that the wrong plan was cancelled, they should be able to easily waive or refund those massive overage charges and restore your correct Pro+ plan. Hope it'll resolve your issue.

[pcoganwu]

Thanks you @AhmadHassan-BTed I have 2 active subscriptions in my account - GitHub Pro+ and GitHub Pro. I have pointed this out in the open ticket. I am waiting for their response.

[AhmadHassan-BTed]

If both are showing up as active, that's 100% the reason your billing is all messed up and crossing wires.

And for their response, you have our well wishes. Don't worry

[pcoganwu]

Thank you @AhmadHassan-BTed

[awdemos]

$22 → $237 → $982 in three months is not a billing error you should have to detective-work your way through. That trajectory is exactly why "usage-based" AI tooling is scary for individuals and small teams: the invoice is a function of how much you happened to code, not a number you agreed to.

Immediate things to do:

1. Open https://github.com/settings/billing and click through to the Copilot usage export. Look for the days that drove the June spike — usually it's a handful of long Agent Mode sessions or premium-model chat threads.
2. Check whether your employer's account and personal account are both being used simultaneously; Copilot billing can attach to whichever context window is active.
3. File a GitHub support ticket with the usage export attached and ask for a line-item breakdown. They can at least tell you which feature burned the credits.

The per-unit rate difference ($0.04 vs $0.01) likely comes from different seat/organization pricing tiers or regional billing, but support is the only place that can confirm.

For teams that can't live with a $982 surprise, the fix is to move the agent workloads to a fixed-price compute layer. We built UltraWork (https://vibecodingagency.com/gpu-cloud/) for that: one monthly price for an H100/A100 GPU workspace, no per-credit or per-unit meter. You know the number before the sprint starts, and it doesn't change because an agent ran overnight.

Not a replacement for Copilot's chat, but a safety hatch when the metered bill stops being predictable.