Let's talk Premium Request Reset

[slikeytre]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

The 1st-of-the-month reset is basically a self-inflicted DDoS. Management complains about server load, but then 'thundering herds' the entire user base into the same 24-hour window. Staggering reset times based on account metrics or billing cycles is Load Balancing 101. Penalizing users for 'bad prompting' is just a distraction from inefficient infrastructure planning.

[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. ⭐

[tmdag]

I am dealing with this exact same issue, and it makes the Pro subscription completely unusable.

Ever since the April 10 changelog update regarding "enforcing new limits," the throttling algorithm has been severely overtuned. I am not running heavy agentic tasks or pasting massive logs; I am doing basic HTML/PHP edits on a single instance and getting hit with 10-minute, 30-minute, and even 3-day lockouts.

Support tickets are returning boilerplate responses blaming "intense usage," but this is clearly a bug in how normal, low-context coding is being classified. We are paying a premium monthly fee and actively losing money on a service we are locked out of. GitHub needs to acknowledge this bug and recalibrate these limits immediately.

[slikeytre]

I've been on the same prompt for 24 hours now, cant even complete 1 task, yes its debug heavy but nothing crazy... Basically 3 hours after rate limit msg buys me 5min of the agent actually doing something then back to the rate limit msg. It's treating everyone like were on free tier, hell when i was on free tier months ago it was better than this. 700 Premium requests left and I can't even consume 1 a day, if this isn't a bug someone needs to be fired. The lack of transparency on what causes rate limiting and the silence on the issue with so many complaining makes me feel like they are intentionally trying to lose customers to solve the problem.

[tmdag]

Just a quick update for anyone else experiencing this: I ended up just canceling my Pro+ subscription today.

Getting hit with 3-day and 30-minute lockouts for basic HTML/PHP edits made the tool unusable for my workflow. I reached out to support, but only received automated replies that didn't address the bug.

It's a shame because it worked flawlessly for the last two months, but I can't justify paying a premium for a service I'm constantly locked out of. Hopefully, GitHub gets the underlying rate-limit infrastructure sorted out soon, but for now, I'm moving to an alternative so I can get back to work.