secondary ratelimit reached??? After two simple text searches? Huh? #141073
Replies: 69 comments 53 replies
-
There is a few of us getting the same. |
Beta Was this translation helpful? Give feedback.
-
il also got it on my phone whithout using any API, simple search on mobile website. not sure it relating to API error. |
Beta Was this translation helpful? Give feedback.
-
Also seeing this when doing a single search via the web UI from the github front page. I literally cannot search for anything because the site is rate limiting me. |
Beta Was this translation helpful? Give feedback.
-
Same. Idk what's happening. |
Beta Was this translation helpful? Give feedback.
-
Getting this on my phone after clicking on one of the languages in my repo's language analysis tab... |
Beta Was this translation helpful? Give feedback.
-
Same here, doing litterally a five chacracter search. |
Beta Was this translation helpful? Give feedback.
-
Same thing here, just going to the GitHub homepage and searching for my repo triggers it. |
Beta Was this translation helpful? Give feedback.
-
I find even i can't get a tool to do something reasonable-- i just stop using that tool. That's likely what I'll do in this case. -RobOn Oct 13, 2024, at 2:24 PM, Valentino Spirito ***@***.***> wrote:
Hey Rob,
The "secondary rate limit" is GitHub's way to protect against excessive use beyond normal rate limits—especially when multiple requests put a high load on their infrastructure. It's less about quantity and more about frequency and potential impact. Even a couple of rapid searches can trigger it, depending on overall server load or other concurrent requests.
You might want to space out your API calls a bit more or use caching where possible to avoid this limit.
Hope this helps!
Valentino
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
💬 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.
-
+1. Same problem from a simple ASCII search. Oddly enough, I've only been having this problem on Librewolf (Firefox fork without the telemetry) and not Firefox itself. So it could be correlated to certain browser privacy settings. |
Beta Was this translation helpful? Give feedback.
-
Also hitting the rate limit. The only thing I did was navigate to github's home page, then try to search for something using the search bar. As far as I can tell, I don't have any erroneous calls being done on my end unless github itself is doing extra calls without my knowledge. |
Beta Was this translation helpful? Give feedback.
-
This has to be a bug. I wasn't even logged in and I get this message on the first search from the Web UI. I also deactivated my VPN so I'm coming from a different IP, not being logged in, and I get this message. Logged in I get the message. About the only way I can navigate to a repo any more is to click a link directly to it or manually enter the URL if I happen to know it. |
Beta Was this translation helpful? Give feedback.
-
You can aslo google ' REPONAME github repo' and find it |
Beta Was this translation helpful? Give feedback.
-
Also getting this on my phone. iOS, Safari. Just trying to view the commit history for a repo. Doesn't matter if it's via 5G, or WiFi. |
Beta Was this translation helpful? Give feedback.
-
The same. Front page, first search, no VPN, no login and getting the rate limit error. If I login it works but this is absolutely not feasible for me. |
Beta Was this translation helpful? Give feedback.
-
Except for one unverified answer it works now for all people answered here. |
Beta Was this translation helpful? Give feedback.
-
Hi, unfortunately I ran into this exact problem just now. |
Beta Was this translation helpful? Give feedback.
-
I ran into this just now. Haven't used GitHub for a few months and when I did..it showed me this message. Nothing GitHub related operation running in background too. |
Beta Was this translation helpful? Give feedback.
-
Just had this issue today. |
Beta Was this translation helpful? Give feedback.
-
Still broken. |
Beta Was this translation helpful? Give feedback.
-
please fix this |
Beta Was this translation helpful? Give feedback.
-
I'm getting this too (secondary rate limit error after a single search query) so still happening in 2025. It doesn't seem to happen when I'm logged-in, though. |
Beta Was this translation helpful? Give feedback.
-
Same for me, I'm guessing that if I search for a long string, it's being treated as a false DoS alarm due to the high frequency of search requests. Also wasn't logged in. |
Beta Was this translation helpful? Give feedback.
-
Same for me. I was browsing a single repository whilst not logged in and clicked on the history button to see commits. This triggered the "Exceeded Secondary rate limit" error noted by the OP. This was the first time I've used Github today from this machine and from this network (home network). To the extent it helps debugging I arrived at the repository from a google search, not from the search functionality on Github. |
Beta Was this translation helpful? Give feedback.
-
OK, lets quote Super Mario: Here we go again, yay! ![]() Seems like many of us have this problem again. I just write a ticket to Guthub support again. Their services are barely usable in this state. Come on and don't let Microsoft make this platform becoming as buggy as Windows! Github is supposed to be our main platform for collaborating ideas, sharing code and encouraging a future in open-source - if we won't act today, this error will last for eternity! |
Beta Was this translation helpful? Give feedback.
-
It's still broken for me and has been for months, if not years. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately it seems Github don't want to help users that don't pay - here is the response I got from support:
If it stays like this, I consider eventually to leave this collaboration platform. |
Beta Was this translation helpful? Give feedback.
-
still broken... or alternatively, this is just by design and this is the new norm as far as rate limits go. Either way it seems untenable. |
Beta Was this translation helpful? Give feedback.
-
This is happening to me as well, and combined with filters not being additive, but replacing my entire search term instead. For example, if I have Instead, it results in just |
Beta Was this translation helpful? Give feedback.
-
Happened here again, while logged out, on the first search attempt (in days or weeks) from the main page. Worked fine when logged in. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
"Whoa there!
You have exceeded a secondary rate limit.
Please wait a few minutes before you try again;
in some cases this may take up to an hour."
I received this msg after performing two simple searches for "1821" in the SONiC (NOS) repo -- what is a secondary rate limit?
Yeesh!
https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28#dealing-with-secondary-rate-limits
From TWO simple ASCII searches... C'mon!
-Rob
Beta Was this translation helpful? Give feedback.
All reactions