GitHub Copilot Pro+ "rate limited" for hours (user_weekly_rate_limited) #192485
Replies: 71 comments 101 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.
-
|
Here one: openai/codex#17738
Copilot Pro+ rate limit for 2.7 week! GitHub/Microsoft must explain this urgently |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Also hit the weekly rate limit after 1 days use. But also now no other model is working in VS, just sits there with the three dots doing nothing. |
Beta Was this translation helpful? Give feedback.
-
3 easy steps to solve the rate-limit problem:1:
2:
3:
I blocked GitHub from my credit card, I will not pay a single cent, I'm done with Fyoumicrsoft. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
да это жопа полная раньше просто рейт лимит был сейчас недельный лимит хоть по 350$ в месяц туда сливаю - надо что то менять и искать альтернативы |
Beta Was this translation helpful? Give feedback.
-
|
If this is will not be fixed, the better way - move to OpenRoute |
Beta Was this translation helpful? Give feedback.
-
|
Microsoft demonstrating how to speedrun losing your entire user base in a week. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/orgs/community/discussions/192707#discussioncomment-16588856
|
Beta Was this translation helpful? Give feedback.
-
|
What was a tool, has become "owned" by Github and they decide if you can use it or not.... Even though we have paid for it and even through we are willing to pay for premium requests once the quota is used up for the month, they have made a tool something you feel like is not a tool anymore but something you have to wait on for it to turn up... like a taxi driver you are waiting on when you are in a hurry to the airport and does not turn up on time and instead takes its time and is late and then takes 15 pit stops before its destination >> and expects full fare to be paid!!! How are we supposed to use this for business when you just turned it off! I am sure your (Github) terms and conditions were written to allow you to do this, but you are essentially killing your client base who are serious about using and paying for it...... Is this a clear "we dont care about you - just f%^&* off and find somewhere else" signal.... You can not get around the weekly rate limit, not even pay for it to keep going >>>> YET ANYWHERE ELSE THERE IS NO SUCH THING that would block you constantly due to a weekly rate limit > you pay for it..... WHY WOULD THEY KILL THEIR CUSTOMERS FAITH AND TURN THEMSELVES INTO THE UNRELIABLE TOOL THAT SAYS WAIT x MINUTES AND THEN AFTER 30 SECONDS IS RATE LIMITED AGAIN!! SERIOUSLY! I CAN ONLY IMAGINE THE AMOUNT OF PEOPLE EXITING COPILOT NOW AS YOU HAVE FORCED ME TO DO THAT IN ORDER TO KEEP MY BUSINESS WORKING................ MAYBE I SHOULD FIND IN YOUR TERMS WHERE I CAN CLAIM DAMAGES FOR NOT BEING ABLE TO DO WORK AND CAUSING ISSUES AS A RESULT OF WHAT I HAD ALREADY PAID FOR.... NO WAY OUT AND STUCK AND FORCED TO LITERALLY HATE THIS COMPANY AND FIND ANOTHER SOLUTION.... SQUEEZED OUT?? WHY WOULD THEY DO THAT? if you need to charge more then why are you not doing that instead of squeezing customers to go elsewhere.... obviously not interested in customers and have another agenda, that is the only thing that makes sense.... When the tool does work, it is fast and works timely, so there is no degradation of the product that i had noticed previously at all so why have they done this??? |
Beta Was this translation helpful? Give feedback.
-
|
I guess Microslop is at it again. I'm locked out. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. Account: hohlfelduglum518-prog, Pro+, hit with Could a GitHub staff member please review and reset? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
To whoever is supposedly managing this "premium" service, Let’s get one thing straight: I am paying you $300 to $400 every single month. I pay this exorbitant amount specifically so I don't have to deal with amateur-hour interruptions. Yet, you somehow have the sheer audacity to hit me with a 63-hour and 40-minute rate limit. Are you fundamentally incapable of understanding how a paid subscription works? The fact that a top-tier paying customer is subjected to a 3-day lockout shows a level of technical incompetence in your system architecture that is, frankly, embarrassing. I am paying you premium cash to actually use the service, not to be treated worse than a free-tier user. And your system's automated suggestion to "Consider switching to Auto"? You can keep that completely tone-deaf, useless advice to yourselves. I don't pay hundreds of dollars a month to be mismanaged by a broken algorithm. This isn't a service; it is a complete joke. You are charging premium prices for an utterly garbage user experience. Fix this catastrophic failure immediately, or I will take my money to a competitor who actually knows how to run a functional platform. |
Beta Was this translation helpful? Give feedback.
-
|
I openly recommend a more sensible use case to everyone: renting GPUs by the hour from places like Hetzner or Vast. If my calculations are correct, for $400 a month I can use the Qwen 3.6 (0.8-1.2K tps 35-3b) and Qwen 3.5 (0.4K tps 120-12b) models indefinitely for 8 hours a day. I can turn them off at night and avoid wasting money. |
Beta Was this translation helpful? Give feedback.
-
|
Github copilot pro and its rate limiting after just 2-3 prompts both weekly and daily waiting hours its now literally useless |
Beta Was this translation helpful? Give feedback.
-
|
Github Pro user here. Ran into my weelky session after 15 or so prompt using a 0x model (GPT-4.1). This is absolutly unacceptable. Microsoft just destroyed the only "Copilot" product people actually liked. The fact this issue happened so sudently with no warning or notice is unacceptable, the capacity and/or money issue didn't suddenly appear, it was slowly building and Github & Microsoft didn't have the forsight to do anything about it. They could have done: warned users, create other plans, implement less aggressive limilts gradually, limited larger models... just name a few. |
Beta Was this translation helpful? Give feedback.
-
|
I found the perfect solution (for me). Not advocating for it, but just to let you know. |
Beta Was this translation helpful? Give feedback.
-
|
What kind of nonsense is this, man! You're even putting a "rate limit" when I want to use the openrouter model, what a disgrace! Fuck you Microsoft! |
Beta Was this translation helpful? Give feedback.
-
What kind of jokes
|
Beta Was this translation helpful? Give feedback.
-
|
Why do I even pay for a fixed ammount of requests when I get rate limited non the less? |
Beta Was this translation helpful? Give feedback.
-
|
This is abnormal — I got rate-limited for 84 hours. I’m leaving Copilot for good. What code assistant would you guys recommend? |
Beta Was this translation helpful? Give feedback.
-
|
*Disclaimer : the post is "discussion type" and does not intend harm in any ways to anyone. It merely provides opinionated feedback. The single best reason for me to use copilot was that it offered different models at better rates. Hold on, i know where this is going. copilot targeted "Request Based Pricing" .. meaning if it thought that the request is not over, it did not use my request. so yes it used a lot of requests for Q&A. but copilot never targeted that. so that was inefficient and was expected. It excelled at development. creating tasks itself and then executing them. so overall with this structure, copilot pricing was unbeatable if used efficiently. however, microsoft soon understood that if the model requires editing more files, then it will use more tokens. so in that case users are not the los*rs, but the company is. So, "Introducing rate limits". in disguise of better stability. now the true users are losrs. no matter how much you are paying, you can't get what you paid for. Why?? because if you do get what you paid for, their hidden margins are gone. that's why they say that use auto mode, so they will give you claude haiku 4.5 or gpt models which we know won't do the tasks. so 10% discount, and will use 25% more requests, and ultimately you will use 15% more requests .. and not to mention you are still being rate limited. But there are genuine reasons right?
But in reality, those are actually the problems that are in the brackets. problem solved. (Rate limits) (a bit of sarcasm ahead*)
Good.. Now users can't use the product, but payment is coming through. Revenue.. Revenue.. ✅✅✅ Now, coming to the real solution based on my opinion, All this comes to only one key usage issue.. people using too many tokens on request based plans. then why don't just make it tokens based? track them, show limits transparently. just like claude code does. I think being transparent results in better user satisfaction then degrading user experience in the shadows. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
This change is bizarre, not only is imposing these new limits a frustrating re-negotiation of the terms of our subscription, the implementation is super flawed. For one thing, I didn't get any sort of indication that there was a rate limit until I hit it, apparently they didn't bother making that work on a few weeks out of date VS Code install. But also, why would the rate limit window be so big? It's one thing to prevent flooding by limiting requests per minute, and I can see having account-level token limits. Heck, you can even rate limit by artificially slowing responses down a bit. But being able to hit a weekly limit and then just... you can't use the tool at all for a week? That's nonsense. Especially since it's easy to hit that limit in a single day! Just last night I decided to try using the agent to build a full project for the first time, and I'm already at my weekly limit? That doesn't make any sense at all. And how is upgrading to a plan that costs four times as much a solution? I apparently can't just buy credits or something, the only way to life the limit is jumping to a much much higher plan tier? I don't need/want this much AI usage all the time, I needed it for this one project and now I'm stuck. EDIT: Also, now that I updated VS Code to a version that fully supports this new nonsense I'm having all sorts of fun new bugs! Agent terminal sessions are super broken, and the agent keeps just spinning trying to get stuff to run and trying to debug phantom issues that are caused by the software not by the code it's writing, which means it's wasting my now very finite request limit going in circles just because the extension has more bugs than a beehive. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Just happened to me while refactoring code for my website. I was in the last few steps (debugging an api call) and it says I'm rate limited but won't say when I can try again. I've been waiting over 5 hours now. Sorry, you have been rate-limited. Please wait a moment before trying again. [Learn More] |
Beta Was this translation helpful? Give feedback.
-
|
Just 1 request now rate limit. What the hell is all this. |
Beta Was this translation helpful? Give feedback.
-
|
got this mail today Hi there, You're receiving this because you have a Copilot Pro or Pro+ subscription, and we want to notify you of some important updates. GitHub Copilot isn't the same product it was a year ago. It has evolved from an in-editor assistant into an agentic platform capable of running long, multi-step coding sessions, using the latest models, and iterating across entire repositories. Agentic usage is becoming the default, and it brings significantly higher compute and inference demands. To keep up with the way you use Copilot, we're transitioning to usage-based billing, and we want to give you enough time to prepare. If you're also an admin on a Copilot Business or Enterprise plan, you'll receive a separate email covering what's changing for your organization. Last week, we made temporary updates to Copilot individual plans to improve reliability and performance ahead of the broader move to usage-based billing. We will loosen usage limits once usage-based billing is in effect. What's changing on June 1 To help you prepare for usage-based billing, we're launching a new billing preview page in early May that lets you calculate what April's usage would have been under the new billing model before it takes effect. You can find more details on usage-based billing in our blog post and FAQ. We appreciate your patience as we build a more sustainable Copilot for everyone. The GitHub Team |
Beta Was this translation helpful? Give feedback.
-
|
Guys they literally want us to cancel our plans, that's the whole point. They want to move away from single users to enterprise and use resources over there. That's what makes sense to them. That is why all this crap. Aggressively rate limit users and make them change plans or make them cancel so they can move to enterprise customers. The new change they made, basically makes it useless Are you kidding me??? |
Beta Was this translation helpful? Give feedback.






















Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Copilot in GitHub
Body
It's absurd that I pay for GitHub Copilot Pro+ and getting rate limited due to "user_weekly_rate_limited". Today is Tuesday and I had yesterday "Copilot Premium Request
180 requests".
GitHub shifting the blame to users because their infrastructure is useless and instead of limiting enterprises we paying individuals are forced to use "auto" models (GPT) and "ghosting" paying users with error messages like "Sorry, you have been rate limited... user_weekly_rate_limited".
It's hilarious and I strongly consider canceling my subscription.
githubstatus.com intentionally avoid mentioning this while users flooded social media with the same problem. Some users reported well over 200 hours "lockout" which is well over a week.
GitHub basically trolling us.
Beta Was this translation helpful? Give feedback.
All reactions