Copilot Student quota bug - Blocked immediately after May 30th reset

[JoanBlancoDev]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Billing & Payment Issues

Hi everyone,

Hi everyone,

I'm facing a frustrating issue with my GitHub Copilot Student account.

My billing cycle resets on the 30th of each month (so it theoretically reset on May 30th). However, today is only June 2nd, and after very light use over the last 48 hours, I am already blocked due to "quota/token limit exceeded".

It feels like my quota never actually refreshed on May 30th, or the system carried over a restriction from my previous month, immediately wiping out my entire new monthly limit in just 2-3 days of normal coding.

Has anyone else experienced this specific bug with the reset dates? Is there a way to get a staff member to look into my account logs and manually restart the quota?

Username: JoanBlancoDev

Thanks for any help or guidance!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[dominator959]

Hi @JoanBlancoDev,
Sorry you're hitting this so early in the month — this is a known recurring bug with GitHub Copilot (especially on the Student/Developer Pack tier). Many users have reported the exact same issue where the quota doesn't properly reset on the expected date (30th in your case), and the system carries over the previous month's restriction.
Quick things to try right now:

Re-verify your Student benefit (this has fixed it for several people):
Go to: https://education.github.com/pack/redeem/copilot-student
Redeem/refresh the Copilot Student offer even if it says it's already active.

Sign out & sign back in everywhere:
In VS Code: Command Palette → Copilot: Sign Out, restart VS Code, then sign back in.
Also sign out/in on GitHub.com in your browser.
Clear any cached credentials if needed.

Check your actual usage page:
Go to github.com/settings/copilot and see what reset date and usage % it shows.

Long-term fix:
This is almost certainly a backend sync issue on GitHub's side. The best way to get it manually reset is to open a support ticket:
→ https://support.github.com/contact/account
Select Billing, payments, or receipts → explain the situation (mention your reset date is the 30th, it's only June 2nd, very light usage, etc.).
Include your username JoanBlancoDev and screenshots of the error + your Copilot settings page.
Unfortunately, there's no reliable self-service "reset quota" button, but support has resolved these reset failures for many users in the past.
You're not alone — this bug has been popping up for months with different reset dates.