Unable to Create Codespaces despite GitHub Pro Resource Quota

[RockYe8]

Select Topic Area

Question

Body

Hello everyone,

I am experiencing an issue where I am unable to create Codespaces for my GitHub Pro account, despite having unused resource quotas. When trying to create a Codespace for my repository, I receive the following error message:
"You are out of monthly free usage or have exceeded your budget for Codespaces."

1. GitHub Pro Subscription: Includes 180 core-hours of Codespaces compute and 20GB of storage.
2. Billing and Usage: My dashboard shows $0 consumed usage this month, with no resources reported as consumed.
3. Repository Details: The repository is public and contains basic content (README.md).
   I have verified my billing dashboard and resource quotas, logged in and out of GitHub, and attempted creating the Codespace multiple times without success.
   I believe this could be a technical issue or a resource allocation error. Any insights from the community or GitHub support are appreciated.

[healer0805]

This looks less like actual usage exhaustion and more like "a billing/entitlement state mismatch" on GitHub's side.

A few things worth calling out:

• That error message is generic and often shown even when usage is "0", especially if the Pro entitlements didn't attach cleanly to the account.
• Public repo + minimal content rules out repo-level restrictions.
• Logging out/in and retrying won't fix it if the backend thinks your Codespaces budget is unset or disabled.

Things that sometimes unblock it:

• Double-check that "Codespaces billing is explicitly enabled" under "Settings -> Billing -> Codespaces" (even on Pro).
• If you recently upgraded to Pro, there can be a "delay or failed entitlement sync".
• Try creating a Codespace from a different repo (even a fork) to rule out a repo-specific flag.

If all usage shows $0 and quotas are unused, this usually needs "GitHub Support to resync entitlements". Several people have hit this where the UI shows Pro benefits but Codespaces is effectively disabled behind the scenes.

At this point, opening a support ticket with screenshots of the billing page and the exact error is the fastest path — it's not something you can fix client-side.a

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬