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

[ductaiii]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Is anyone else getting this error with model 0X?

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

[dw7086]

一个小时还没恢复，pro+

[KaiXuanSama]

pro用户依旧收到这个所谓的速率影响，我请问了我不是pro吗？

[Xiaochaosui]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Is anyone else getting this error with model 0X?

I also encountered this problem, have you solved it?

[ductaiii]

Not yet. I think this is a system-wide bug affecting everyone, but I just switched to Auto mode and it works fine

[583]

I encountered the same problem. Pro+

[peoples111]

我的gpt5.3 codex请求数跟你不一样，我是0.9。why？🧐

[583]

我的gpt5.3 codex请求数跟你不一样，我是0.9。why？🧐

你是auto模式下运行所以0.9

[RockLiu73]

You've hit your global rate limit. Please upgrade your plan or wait 3 hours 42 minutes for your limit to reset. Learn More

我認為是 subagent 導致這個問題，不該這樣限制訂閱戶吧~ 這次我並沒有開多個 session 同時跑，而是每一個 Request 接續執行

[kvn-7]

Same here with Pro+

[brillian32]

Same here with Pro+ , bug？ Could it be that the vulnerability was written by AI?

[lh18578783165-cloud]

也

[YongqiYin]

same

[xlfdyzcs]

Same here with Pro+

[pattrawan-po]

Yea, I have same issue. I just upgrade to Copilot Pro+ yesterday.

[gyi73039-beep]

没跟我开玩笑吧，我刚开的P+，才用了3.7%就直接限制了，也不知道找谁处理，换模型也是这，那这个订阅存在的意义是什么

[banhdepchai]

Update the plan, my friend

[ductaiii]

@banhdepchai i think it's a global system bug. Looking at the comments, even Pro+ users are affected, so it's definitely not a subscription plan issue.

[xlfdyzcs]

How can we contact staff to pay attention to this issue so that they can restore it in a timely manner?

[sirumsk]

Same here i've pro + still have 30% usage.

[aoeiuvb]

The appearance of so many people makes me feel that there is a problem with the Copilot service.

[zaevi]

It looks like GPT-5.4, Sonnet 4.6, and Opus 4.6 are all down.
I switched to Auto mode and it works. It's currently using GPT-5.3-Codex.

[apisek-b]

I use pro plan but I got the same issue

[esthrim]

same here

[xjxy666]

I had the same problem, but I have recovered now. It seems like a bug

[StemCell512]

Now my copilot is working again. Not sure whether the bug has been fixed or I just "waited for my limit to reset" XD

[Akash1134]

We sincerely apologize for the disruption you may have experienced earlier today.

For a period of a few hours, a service-side issue impacted some users and may have caused unexpected errors or interruptions. Our team quickly identified the root cause and has since implemented a fix to fully resolve the issue.

We are actively reviewing what happened and taking steps to strengthen our systems to help prevent similar issues in the future. Thank you for your patience and for bearing with us while we worked to restore normal service.