Unexpected Codespaces/Codebase billing & access error on GitHub Pro account

[NullNaveen]

Select Topic Area

Question

Body

Hello ,

I’m on a GitHub Pro plan. I believe Pro includes a large allotment of Codespaces hours (I think ~180 hours / certainly >100 hours), but I’m seeing unexpected behavior and a billing error preventing access.

What happened

On Nov 16, 2025 I tried to open my codespace and got this message: “you seem to have a billing issue please adjust your billing settings to continue using code bases” (exact wording from the UI).
I only opened the codespace once earlier this month and closed it. I have not used the codespace since then.
Despite that, the usage chart for November shows a steady upward trend from Nov 1 and indicates ~$5 in Codespaces/Codebase usage. I don’t understand why usage is increasing daily when I haven’t been opening a codespace and all the codespaces are inactive for more 10 days.
I checked Settings → Billing but could not identify any obvious billing problem or setting I could fix.

Please check my account and confirm why I’m seeing the billing error and what specifically triggered it.
Provide a breakdown of the billed Codespaces/Codebase usage for November (timestamps, workspace/instance names or IDs, duration, and whether that usage applied to my Pro included hours or was billed as overage).
If the charges or the billing block are incorrect, please reverse or correct them and restore my Codespaces access.
Tell me any steps I should take to prevent unexpected background usage (e.g., orphaned workspaces, running instances in an organization, subscription settings).

[iyawnnn]

It looks like your GitHub Pro account is encountering a billing block because the system detected usage that exceeded your included Codespaces hours or triggered a billing check, even if you haven’t actively opened a codespace recently. Sometimes, inactive or orphaned workspaces, background processes, or instances in linked organizations can continue accruing usage, which may show up in your billing chart. To resolve this, you’ll need to contact GitHub Support directly so they can review your account, provide a detailed breakdown of all Codespaces usage for November (timestamps, instance IDs, durations, and whether it counted against your Pro allowance or overage), correct any erroneous charges, and restore access. To prevent unexpected charges in the future, ensure all inactive workspaces are deleted or stopped, check organization-linked instances, and verify your subscription and billing settings.

[NullNaveen]

How to contact GitHub Support directly

[iyawnnn]

You can contact GitHub Support directly by following these steps:
1. Go to the GitHub Support Contact page.
2. Choose the appropriate topic—for your case, select “Billing & Payments”.
3. Fill in the form with your account details, describe the issue (include that it involves unexpected Codespaces billing on a Pro plan), and attach any screenshots if helpful.
4. Submit the request.

After submission, GitHub Support usually responds via the email linked to your account. Be sure to mention your Pro plan, the date you first noticed the billing issue, and that you need a breakdown of Codespaces usage and restoration of access.

[shinybrightstar]

👋 Welcome to the GitHub Community, @NullNaveen! Congratulations on your first post! 🎉

You can find solutions to most billing issues in our 💳 GitHub Community Discussions Billing & Subscription Guide. For Codespaces billing, you could check out the GitHub Codespaces billing documentation

If you need more help, the best place to get answers is by opening a ticket on our Support page.

Best of luck!