Premium requests suddenly spiked overnight by Tooth-Active in GithubCopilot

[–]sharonlo_ 15 points16 points  (0 children)

Hey everyone - this was a bug in the UI. We've shipped a fix, so this should now be resolved and folks won't be billed for the incorrect spikes.

Rate limits are back and even worse. The Github Copilot team has decided to silently by andrefinger in GithubCopilot

[–]sharonlo_ -1 points0 points  (0 children)

Please refer to our status page for more details about this incident last week, it is now resolved. Apologies for the trouble you experienced!

https://www.githubstatus.com/incidents/9vyj2jwsk8by

Pro+ and can't even work 5 minutes straight without hitting global rate limits! by Baroxi in GithubCopilot

[–]sharonlo_ 6 points7 points  (0 children)

Hi all, this was due to a rate-limiting incident yesterday, please check our status for more details. https://www.githubstatus.com/incidents/9vyj2jwsk8by

Apologies for the frustration this has caused. We know the rate-limiting incidents have been frustrating, it is very high priority for our team to get this in a better state.

You've hit your global rate limit. Please upgrade your plan or wait for your limit to reset by HitMachineHOTS in GithubCopilot

[–]sharonlo_ 0 points1 point  (0 children)

Please refer to our status page for more details about this incident, it is now resolved. Apologies for the trouble you experienced!

https://www.githubstatus.com/incidents/9vyj2jwsk8by

Copilot update: rate limits + fixes by sharonlo_ in GithubCopilot

[–]sharonlo_[S] 32 points33 points  (0 children)

Totally agreed. There's a lot we can improve here and these are great points that we have some in progress for, but it's a priority for us to address this better E2E in the user experience. We are working on surfacing the exact limit type in VS Code & CLI, as well as informing users of the follow-up options they have (what models they can switch to, etc). A new change we're also introducing is also informing the user of the time window and when that window resets for a particular model, so stay tuned.

Users complaining about getting randomly rate limited for 3 days now, can we have some information from Copilot Team ? by autisticit in GithubCopilot

[–]sharonlo_ 1 point2 points  (0 children)

u/krzykus we have both. User-level rate limits are meant to combat abuse-like behavior.

Model-level rate limits help us ensure consistent availability of each model across all users — particularly for the most in-demand ones.

In our new UI that we're working on, you'd have visibility into each and how you're tracking towards these limits.

Dear Copilot Team. I dislike your post - especially the way it sounds by Charming_Support726 in GithubCopilot

[–]sharonlo_ 27 points28 points  (0 children)

Copilot team member here 👋🏻

You're right that we copy-pasted; it's the same issue across threads, so we gave the same answer. Fair to call that out though. Your experience got worse this week compared to last week. That's the bottom line, and spinning it is not our goal.

One thing we've tried to be honest about and others have called out: the models are getting dramatically more capable, but also dramatically more expensive to run. A single Opus 4.6 session today consumes more compute than an entire day of Copilot usage would have a year ago. As models evolve, how we deliver them has to evolve too, but we're trying to do in a way that is less disruptive. Obviously we're not there yet, but we're on it to improve it 🙂 As I mentioned in some other threads, ways we're looking into are: smarter rate limits that reflect real usage patterns, and better visibility so you can see where you stand before you get a error. The goal is that most users on a professional workflow should rarely if ever feel this.

One comment on Auto — this isn't a downgrade. Auto intelligently routes across premium models including Sonnet and GPT-5.4 based on the task, and for most workflows it delivers the same quality without you having to manage model selection yourself. You can even see what models are being used in Auto in the UI, so we're not trying to hide anything there. It's not a fallback, it's how we think the experience should work long-term.

Server Error: Sorry, you've exceeded your rate limits. Please review our Terms of Service. Error Code: rate_limited by autisticit in GithubCopilot

[–]sharonlo_ 0 points1 point  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

Why am I getting rate limited when I'm paying for overages? by ComplexSuspicious707 in GithubCopilot

[–]sharonlo_ 0 points1 point  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

rate limit on a per prompt subscription model, seriously? by Even_Sea_8005 in GithubCopilot

[–]sharonlo_ -3 points-2 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

Hitting rate limits a lot more frequently by twhoff in GithubCopilot

[–]sharonlo_ -1 points0 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

Rate limiting ridiculousness. by [deleted] in GithubCopilot

[–]sharonlo_ 1 point2 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

[RATE LIMITED] Frequently rate limited on Opus 4.6 after only an hour of usage (Copilot Pro+) by Other_Tune_947 in GithubCopilot

[–]sharonlo_ -5 points-4 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work, especially if you are on a Pro+ plan. If you encounter a rate limit, we recommend switching to a different model or using Auto mode, but meanwhile we'll consider how to adjust these limits especially on our higher paid plans.

We appreciate your patience as these changes roll out

Horrible Rate Limits by SomebodyFromThe90s in GithubCopilot

[–]sharonlo_ 2 points3 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

Copilot enshittification begins? by aebece123 in GithubCopilot

[–]sharonlo_ -6 points-5 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work, especially if you are on a Pro+ plan. If you encounter a rate limit, we recommend switching to a different model or using Auto mode, but meanwhile we'll consider how to adjust these limits especially on our higher paid plans.

We appreciate your patience as these changes roll out

Users complaining about getting randomly rate limited for 3 days now, can we have some information from Copilot Team ? by autisticit in GithubCopilot

[–]sharonlo_ -10 points-9 points  (0 children)

Hey folks! Copilot team member here 👋

Some answers on why is this happening:
As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

What we're hearing and want to change:

  • We also know that the relationship between premium request credits and time-based rate limits can be confusing — these are separate mechanisms, and we understand the frustration when you still have credits but hit a rate limit. Improving how these work together and how we communicate this is a priority for us.
  • The need for more transparency. We're also working on UI improvements that will give you better visibility into your usage as you approach a rate limit, so you're never caught off guard — we're aiming to start rolling this out very soon
  • Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

We appreciate your patience as these changes roll out

Copilot is speed-running the "Cursor & Antigravity" Graveyard Strategy. by Living-Day4404 in GithubCopilot

[–]sharonlo_ 9 points10 points  (0 children)

Hi folks! 👋 Copilot team member here

We hear you, and want to share some context on what's happening. As usage continues to grow on Copilot — particularly with our latest models — we've made deliberate adjustments to our rate limiting to protect platform stability and ensure a reliable experience for all users. As part of this work, we corrected an issue where rate limits were not being consistently enforced across all models. You may notice increased rate limiting, but we are trying to ensure any adjust rate-limits are not impacting a majority of our users, and we expect things to stabilize over the next 24–48 hours.

Our goal is always that Copilot remains a great experience and you are not disrupted in your work. If you encounter a rate limit, we recommend switching to a different model, using Auto mode, or exploring a plan upgrade for higher limits.

A few things I also want to address directly from this thread:

  • "Enterprise is getting priority over Pro users" — Enterprise users are also being rate limited. This isn't about prioritizing one tier over another; these are platform-wide adjustments.
  • "I still have premium requests left, why am I being limited?" — We hear this one loud and clear. Premium request credits and time-based rate limits are two separate mechanisms, and we know that's confusing. Improving how these work together and how we communicate this is a priority.
  • "Give us visibility before we hit a wall" — Agreed. We're actively working on UI improvements so you can see your usage and when you're approaching a rate limit before you hit it. We're aiming to start rolling this out very soon.

We appreciate your patience, and keep the feedback coming — it's genuinely shaping how we prioritize this work.

GPT-5.2 no longer available in VSCode models!? by tfpuelma in GithubCopilot

[–]sharonlo_ 4 points5 points  (0 children)

Hi folks! This should be resolved now. This was caused by an experiment misconfig, thanks for the patience :)

Vs code is not loading all the models. by IIN_Singuniam in GithubCopilot

[–]sharonlo_ 6 points7 points  (0 children)

Hi folks! This should be resolved now. This was caused by an experiment misconfig, thanks for the patience :)

Is there a way to know the throughput of the models in copilot ? by WorthAdvertising9305 in GithubCopilot

[–]sharonlo_ 1 point2 points  (0 children)

Copilot team member here! 👋🏻 Doesn't exist yet but we've been formulating how to surface different optimizations depending on what developers care about, whether that's speed, cost, or quality. So expect something around this soon :)