38 HOUR RATE LIMIT?!?!?! #192678
Replies: 14 comments 21 replies
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Numerous other people are having this problem. If this is not remedied soon I suggest cancelling. The only way they'll learn is if you vote with your wallet. Don't expect a response from GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
Why do i get the feeling they did this so users would go somewhere else,
freeing up usage?
because the whole "Fairness" thing is BS. People who pay for Pro+ get
better rates than those who don't...
this is the whole "Equity" BS corporate entities like to push on people
after telling them "You get more as a Pro+ member, just pay us more money"
all just so they say, "We rate limited you for 181 hours so people who
didn't pay anywhere near as much can get the same quality"
Delusional...
…On Wed, Apr 15, 2026 at 9:33 AM pepperymilkcap ***@***.***> wrote:
Numerous other people are having this problem.
#180092
#192435
Don't expect a response from GitHub.
*This is fraud at this point. People are paying monthly to access a
service and are not being able to.*
—
Reply to this email directly, view it on GitHub
<#192678 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVUICWHKAAQRMEI5IZ75IN34V6FUFAVCNFSM6AAAAACX2HZTZSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJXGEYDAMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Wenn ihr die aktuelle Entwicklung von [Claude.ai] verfolgt, seht ihr, dass das Rate Limit dort schon etwas länger integriert ist. Natürlich schaut die Konkurrenz genau hin, und gleichzeitig stehen die Unternehmen in Amerika im ständigen Austausch. Es war also nur eine Frage der Zeit, bis Microsoft – als börsennotiertes Unternehmen – nachzieht. Was Microsoft meiner Meinung nach nicht ganz durchdacht hat: Die meisten Coder nutzen Claude.ai bereits ohne Copilot. Durch die Einschränkungen fällt der Absprung zu Claude nun sogar noch leichter. Aktuell gibt es auch in der VS Code Insider-Version kein Update dazu, weshalb das Problem vorerst bestehen bleibt. Es sei denn, die Programmierer laufen schneller weg, als es Microsoft lieb ist! If you've been following the development of [Claude.ai], you'll see that the rate limit has been integrated there for some time. Naturally, the competition is watching closely, and companies in America are in constant communication. It was only a matter of time before Microsoft—as a publicly traded company—followed suit. What I think Microsoft hasn't quite thought through is that most coders are already using Claude.ai without Copilot. These restrictions make switching to Claude even easier. Currently, there's no update for this in the VS Code Insider version, so the problem will remain for now. Unless, of course, the programmers abandon it faster than Microsoft would like! |
Beta Was this translation helpful? Give feedback.
-
|
Same here. I’m also a paying user, and what makes this worse is that the lockout is not just a minor slowdown — it turns into tens of hours of unusable access after hitting a weekly limit. A 38-hour wait on a paid developer tool is not a reasonable premium experience. In my case, I’m not just paying the base subscription either. I’ve already spent significantly more through premium requests, yet the system still behaves as if the answer is simply “upgrade” or “wait.” That stops making sense very quickly. The issue is not that limits exist. The issue is that paying users are being pushed into long lockouts without clear transparency on what the real usable limits actually are. GitHub needs to explain how these weekly lockouts are calculated and why this is considered acceptable for paid plans. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, we appreciate you reaching out to report this issue. We have recently needed to pause GitHub Copilot Pro trial plans due to a significant rise in abuse of our free trial system, as announced on the GitHub Blog: Pausing new GitHub Copilot Pro trials. Wanted to re-emphasize that this is a temporary pause. We are actively working on improved safeguards to prevent misuse of the trial system ⭐ We are aware that some users are having trouble cancelling the trial and we are working towards a solution. For more information and real-time updates, please subscribe to this discussion to receive notifications as we post additional details. |
Beta Was this translation helpful? Give feedback.
-
|
Keeping all of this buried in forum threads helps no one. More people should share their screenshots and experiences on X and LinkedIn so this issue gets proper visibility. Paid users deserve transparent limits and consistent communication. #FixCopilotLimits |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. Subscribed Copilot Pro+ and based on my usage overview, I have clearly not reached my rate limit. Since 3 days I'm blocked by rate limit issue. Support questions completely ignored. I cancelled by annual subscription and asked for refund. No response. What difficulties does Github has to not able to communicate clearly to their paid customers what's currently going on? This is so insane! |
Beta Was this translation helpful? Give feedback.
-
|
I think Github is deliberately down-voting discussions they don't like. I posted a discussion item 30 minutes ago and it is already halfway down the page: https://github.com/orgs/community/discussions/192773#discussion-9893366 |
Beta Was this translation helpful? Give feedback.
-
|
There's a couple threads on hacker news, I suggest to upvote / comment them to gain visibility: |
Beta Was this translation helpful? Give feedback.
-
|
well I'm not getting the 38 hour rate limit anymore, but still getting the weekly rate limit and having to wait an arbitrary 10-20 minutes before I can proceed again. they're just petty at this point. |
Beta Was this translation helpful? Give feedback.
-
|
now I'm kicked off for 3 MORE DAYS... at least it's not telling me how many hours anymore
|
Beta Was this translation helpful? Give feedback.
-
|
i have pro+ |
Beta Was this translation helpful? Give feedback.
-
|
At this point I'm looking into Class Action Lawsuits. I didn't pay for Rate Limits, I paid to NOT GET THEM. and GitHub clearly doesn't give a sh*t about its users or paid subscribers. |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
VSCode
Body
Are you serious? I have a 38 hour rate limit because I hit my Weekly limit??
Are you serious?
Beta Was this translation helpful? Give feedback.
All reactions