Obscenely Long Rate Limits (Over 24 Hours) and Possible Distillation False Positive #192435
Replies: 48 comments 131 replies
-
|
66 hours!!!!! paying enterprise prices for a single person on copilot pro+ you all are F*ing insane!! |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue ^ |
Beta Was this translation helpful? Give feedback.
-
|
No solution as of yet. Resorted to auto mode and am getting sub-par code quality. |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps related? |
Beta Was this translation helpful? Give feedback.
-
Of course I have, that's why I'm paying you (GitHub) to get rid of the limits. I won't pay more to increase my "weekly rate limits" as well if I'm just a hobbyist who's ALREADY SUBSCRIBING, so that's not my problem and I don't care how, but solve it. And if you want to punish people for wanting to do something - while you yourself are being greedy - then... maybe it's time to say good bye to any cash that was going to you, and use a local LLM instead? |
Beta Was this translation helpful? Give feedback.
-
|
不知道有什么办法可以解决? |
Beta Was this translation helpful? Give feedback.
-
|
Has anybody had any responses to any support tickets yet? |
Beta Was this translation helpful? Give feedback.
-
Why is GPT 4.1 rate limited too? I can't use any models. This is crazy. I'm on Pro+ |
Beta Was this translation helpful? Give feedback.
-
|
If this keeps up, I'm literally not renewing next month. |
Beta Was this translation helpful? Give feedback.
-
|
It appears that this won't be rectified, so where next? What other services offer similar pricing but actually let us pay and use the service? |
Beta Was this translation helpful? Give feedback.
-
|
Server Error: Sorry, you've exceeded your weekly rate limit. Please review our Terms of Service. Error Code: user_weekly_rate_limited Its just Tuesday! |
Beta Was this translation helpful? Give feedback.
-
|
I canceled my Pro+ subscription beacause of this 33 hours limited WTF!! |
Beta Was this translation helpful? Give feedback.
-
So they're definitely switching between those "rate'limited" models fyi. |
Beta Was this translation helpful? Give feedback.
-
|
Also hit the weekly limit after 1 day, but nothing is working in VS chat, auto or specific model - just hangs on the three dots. |
Beta Was this translation helpful? Give feedback.
-
|
I also encountered this problem. I encountered a rate limit when subscribing to Pro before, so I upgraded to Pro+. However, today while continuing to work on the project, I was directly informed Sorry, you've hit a rate limit that restricts the number of Copilot model requests you can make within a specific time period. Please try again on Apr 20 at 8 AM. Please review our Terms of Service ( https://docs.github.com/site-policy/github-terms/github-terms-of-service ). (Request ID: 84B2:2B0EDA: 150FC41:17B234F: 69DF48DD). Now only the "auto" mode is available, but I only used less than 20% of the credit limit |
Beta Was this translation helpful? Give feedback.
-
|
GitHub are still completely silent on the rate limiting issue. Why are they adding new models from upstream providers (like Opus 4.7) while most of their subscribers are barred from using them? |
Beta Was this translation helpful? Give feedback.
-
|
Now I just keep getting told to wait 4-14 minutes every time I send an Opus 4.6 request. I wait double that time, send a request, then get another 4-14 minute rate limit. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Tried Opus 4.6 again, now it just says "Working" and never does anything. Are they trying to make the rate limits more discreet? Is anybody else experiencing this? |
Beta Was this translation helpful? Give feedback.
-
|
I've been able to send a single Opus 4.6 request. It took a while to respond but I no longer seem to be rate limited. I suggest everybody try again now and we can see if it is truly fixed or if we're just in the "eye of the storm" so to speak. If this is over (and it may not be for everyone), why was this allowed to happen and why wasn't it acknowledged by GitHub? My support ticket still has no response. |
Beta Was this translation helpful? Give feedback.
-
|
This throttling is literally brain-dead. Tasks I could one-shot with Opus 4.6 now take GPT 5.3 Codex like ten tries, and it still misses the mark. Like, what’s the point besides wasting my time and burning my credits? Peak clown-tier business move. I'm unsubscribing after this month; I'd rather pay a premium for something that actually works. 🤯 |
Beta Was this translation helpful? Give feedback.
-
|
Started working as of today, after a bit of usage, several including me got hit with the 20th 2AM / 08:00. Funny (as all got now the same) |
Beta Was this translation helpful? Give feedback.
-
|
same #192880 |
Beta Was this translation helpful? Give feedback.
-
|
You triggered GitHub's distillation/abuse detection, the extended cooldown (24 to 48 hours is the common window) is the enforcement action, not a normal rate limit. The combination that usually sets it off is the same account hitting Opus or another premium model from multiple concurrent sessions, especially when the traffic pattern includes a VPN or a datacenter-adjacent IP. The system can't tell you apart from someone farming credits to resell. A few things worth knowing:
For the support ticket, include the timestamps when you hit the limit, the tools/IDEs you're using Copilot from, and mention you were on a VPN for that quarter-hour window. That gives them enough context to look up your traffic and confirm it was a false positive. Refunds for paid Opus credits burned during the cooldown aren't automatic, ask for them explicitly. The messaging on GitHub's side really needs work though. Landing a "looks like scraping" dialog on a paying customer with no prior warning is bad product. |
Beta Was this translation helpful? Give feedback.
-
|
To the GitHub Copilot Team, I am writing to express my strong dissatisfaction with your recent restrictions. Are you suggesting that a legitimate individual user running Copilot via remote control between remote and local environments is somehow "violating" your terms? This is an incredibly overbearing and unreasonable policy. As a paying subscriber, I expect the service to be available across my development environments, whether I am working locally or accessing my setup remotely. Restricting usage based on the method of access—especially when the intent is legitimate personal development—is a blatant disregard for user experience and a breach of the trust we place in a professional tool. Your current approach feels less like "managing service quality" and more like a forced restriction of a service I have already paid for. I demand a clear explanation for these "intelligence throttling" and access-limiting behaviors. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@Akash1134 Why hasn't GitHub put out a statement on this? Why are paying Pro+ users still getting these extreme rate limits? |
Beta Was this translation helpful? Give feedback.
-
|
Ran into the same thing two days ago, hit a 38 hour cooldown on Opus 4.6 after maybe an hour of real work. Bit of what I've pieced together from going through it: The limit is per-account, not per-model. Switching from Opus to Sonnet while flagged doesn't do anything. Auto mode seems to bypass it but the output quality on longer agentic tasks drops off a cliff. Weirdest part for me was that the Copilot usage dashboard still showed me at around 20% of my monthly budget while I was hard blocked. Whatever signal is driving the cooldown isn't actually tied to the credit number the UI is showing you. For the support ticket, including exact timestamps and which IDE you were in helped me get an actual human response (took about 40 hours). Not a fix, but at least an acknowledgment. Really hope they add a visible counter for this, flying blind on when the block lifts is the worst part. |
Beta Was this translation helpful? Give feedback.
-
|
Copilot CLI ● Changelog for v1.0.32
Auto in Copilot CLI works under /model |
Beta Was this translation helpful? Give feedback.
-
|
Same here. |
Beta Was this translation helpful? Give feedback.












Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Copilot in GitHub
Body
When did these become a thing? I'm a Pro+ customer who consistently pays for hundreds worth of extra Claude Opus 4.6 credits per month. I might consider cancelling if this isn't a bug because I cannot afford to be hung out to dry for days at a time.
I tried switching to Opus 4.5, then Sonnet, but nothing budged.
After a while I attempted to start a chat using the web interface, only to be met with an suspicious half-accusation of scraping:

I've opened a support ticket but was wondering if anybody else has had similar issues? I frequently use Copilot in 1-3 windows simultaneously and used it under a VPN for a quarter of a hour or so earlier.
Beta Was this translation helpful? Give feedback.
All reactions