I have Pro plan, but unable to use Codespace

[FF-crazy]

🏷️ Discussion Type

Question

Body

I have never used Codespaces before. But it says I have used out of quota.



Could you please tell me why and how I can solve this?

[Ayouub-aj]

Hi @FF-crazy,

Since this is your first time using Codespaces, seeing a "quota exceeded" message can definitely be confusing. Even with a GitHub Pro plan, there are a few common reasons why this might happen:

Spending Limit at $0: By default, GitHub sets a spending limit of $0 to prevent unexpected charges. While Pro includes a free monthly allowance (180 core hours and 20 GB of storage), if your account settings have a hard limit of $0, it can sometimes trigger a restriction if the system anticipates any usage beyond the base free tier or if there is a sync delay.

Solution: Go to your Settings > Billing and plans > Plans and usage, scroll down to the Codespaces section, and check your "Spending Limit." Try setting it to a small amount (like $1) to see if it unlocks the service. You won't be charged unless you exceed your Pro allowance.

Organization vs. Personal Account: If you are trying to open a Codespace within a specific repository owned by an organization, the organization’s billing settings apply, not your personal Pro plan. If that organization hasn't enabled Codespaces or has hit its own limit, you'll see this error.

Storage of Unused Codespaces: Codespaces don't just use "compute" time; they also use storage. If you have several stopped/idle Codespaces from previous attempts, they might be consuming your 20 GB storage quota.

Solution: Check github.com/codespaces and delete any existing environments you aren't using.

I recommend checking your Billing & Usage page specifically to see exactly where the "quota" is being flagged (Storage vs. Compute).

I hope this helps you get up and running! If this solves your problem, I’d be very grateful if you could mark this as the official answer so it can help others in the community.

Best of luck with your project!

[shinybrightstar]

Hi @FF-crazy, 👋🏻 thanks for reaching out.

Even if you have GitHub Pro, you still need to complete these two steps to activate Codespaces:

1. Create a Codespaces budget (minimum $1)
2. Set the budget behavior (pause or allow overage)

For a full walkthrough, please refer to our GitHub Codespaces Billing Guide.

Best of luck!

[sophiasmithastri]

It might be worth checking if any background or previously created environments are still counted toward your usage, even if you did not actively use them. Sometimes preconfigured setups or organization-level limits can affect quotas. Reviewing your billing settings or usage details could clarify where the consumption is being recorded and help resolve the issue.

[FF-crazy]

**

**
I tried methods you gays told me. But it seemed not work

[syedsafeer]

"Hi @FF-crazy,
the 'Something went wrong' message in your dashboard is a clear sign of a backend sync error on GitHub's side. It’s not your fault.

Try these 2 simple things:

1. Use Incognito Mode: Open your billing page in a private/incognito window. If it works there, just clear your browser's cache and cookies.
2. Contact Support: Since you have a Pro Plan, you get priority help. Open a ticket at GitHub Support and show them this screenshot. They can manually reset your quota in minutes.

Sometimes the system just gets stuck, and only an admin can 'push' it from the back

[FF-crazy]

I have opened a ticket in 2025.11. But no one replied.

[syedsafeer]

@FF-crazy,

Waiting since November 2025 is definitely not normal. Most tickets get a response within a few weeks at most.
Try this:

1. Check Spam/Junk: Search your email for 'GitHub Support' to see if you missed their reply.
2. Bump the Ticket: If you have the original confirmation email, try replying to it asking for an update.
3. New Ticket: If you still hear nothing, open a new ticket and mention your old ticket number so they can track the history.

Since we are community members, we can't see ticket statuses, but 5 months usually means the ticket might have been lost or closed