GitHub Community
secondary ratelimit reached??? After two simple text searches? Huh? #141073
Replies: 58 comments 40 replies
-
|
There is a few of us getting the same. |
Beta Was this translation helpful? Give feedback.
-
|
I used the searchbox 2x in one evening to get the rate limit warning: Whoa there! |
Beta Was this translation helpful? Give feedback.
-
|
Whoa there! Failing right on the second page of search result: See also: https://github.com/orgs/community/discussions/141770#discussioncomment-11070800 ---- One way in particular prodigal about the bandwidth usage: Why such TH-Hub practice? |
Beta Was this translation helpful? Give feedback.
-
|
Duplicate of: |
Beta Was this translation helpful? Give feedback.
-
|
I got rate limited after 1 search. Just immediately “You have exceeded a secondary rate limit” |
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.
-
|
Simply everything wrong: |
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.
-
|
Does this happen when you are logged in? See github.com top search bar - currently seeing rate limit issues |
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.
-
|
Logged-in vs. no login, supposedly. |
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.
-
|
Ever since Mickeysoft took over, github is getting worse and worse. M$ should just fade away into obscurity. |
Beta Was this translation helpful? Give feedback.
-
|
Only explanation is GitHub is run by people that hate you :) |
Beta Was this translation helpful? Give feedback.
-
|
It also could be that they have more important things to work on, like fixing vulnerabilities or something along those lines... |
Beta Was this translation helpful? Give feedback.
-
|
Today I got an encouraging reply from support (I told you I created an official ticket):
For myself it works now, I can search Github. But I don't want to be selfish, so I ask you: Do you can perform Github searches now when not being logged in without (or at least with less) error messages? |
Beta Was this translation helpful? Give feedback.
-
|
Working for me now on Incog. |
Beta Was this translation helpful? Give feedback.
-
|
For myself it work. But I don't want to be selfish, so I ask you: Do you can perform Github searches now when
not being logged in without (or at least with less) error messages?
(I will tell the support our average result then.)
It did work fine for me now.
|
Beta Was this translation helpful? Give feedback.
-
|
Glad to hear, so its two of us now (from about several millions people) |
Beta Was this translation helpful? Give feedback.
-
|
Working for me as well. Thank you for your effort. |
Beta Was this translation helpful? Give feedback.
-
|
Still broken for me. If I'm not logged in I can't do a search. (Safari, MacOS 14.6.1) |
Beta Was this translation helpful? Give feedback.
-
|
Probably IP related? ---- Try clean the cookies etc. whatsoever. |
Beta Was this translation helpful? Give feedback.
-
|
There is only one way to verify that: Please try using VPN (not Tor browser as it will most probably get blocked) to make sure about that. |
Beta Was this translation helpful? Give feedback.
-
|
Working for me now, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Works for me now |
Beta Was this translation helpful? Give feedback.
-
|
working for me without being signed in! thanks for getting results @Dragodraki |
Beta Was this translation helpful? Give feedback.
-
|
You're welcome! Glad, if I could help. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, not fixed. It happened on my phone this morning.
…On Thu, 7 Nov 2024 at 8:37 am, dude363635 ***@***.***> wrote:
working for me without being signed in! thanks for getting results
@Dragodraki <https://github.com/Dragodraki>
—
Reply to this email directly, view it on GitHub
<#141073 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQ6EMROPW6US3QS2GDNQMZDZ7KDYLAVCNFSM6AAAAABPW3UUBGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJXGEYTENQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
CRICOS Registration
Provider Code 00477G
|
Beta Was this translation helpful? Give feedback.
-
|
They didn't disabled whole protection, so maybe it's only a bad coincidence with your IP address. |
Beta Was this translation helpful? Give feedback.
-
|
Does it work for you by changing the IP or deleting the cookies and reload? |
Beta Was this translation helpful? Give feedback.
-
|
So far we have all positive feedback but one. To make sure I'll wait some days more. @everyone: |
Beta Was this translation helpful? Give feedback.
-
|
Also for me it works now, thank you so much! It's just interesting: After logging out, deleting github cookies and getting a new IP the very first search results in a ratelimit reached error. Simply refreshing the page solves it and following searches also work. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, thats the usual way Github handle requests. Deleting cookies makes Github confused because its the way an hacker would act too and seeing the same IP, Github realize you are the same anyway. It appears also if the IP adress you got had raised suspicion in the past. |
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.
-
|
I just played around with this for a bit. It seems to specifically be a problem with Safari. Searching for the word "test": |
Beta Was this translation helpful? Give feedback.
-
|
I had this problem on Firefox on Windows. After a refresh it worked, then went back to the same problem a two or three searches later. |
Beta Was this translation helpful? Give feedback.
-
|
Would refreshing again outright make it work..? |
Beta Was this translation helpful? Give feedback.
-
The first time I had the issue was the first search I made after not using GitHub search in over a week. After going back to the GitHub homepage and trying again it worked (then stopped working again after refining the search a couple of times.) After logging in, it worked normally. After logging back out, my first search showed the rate limit screen. Hard refreshing did nothing. Going back to the GitHub main page and running the same search again (within 1 minute) worked. This was done without a VPN, from Firefox on Windows, on a home internet connection. No one else uses GitHub from my IP address. |
Beta Was this translation helpful? Give feedback.
-
|
Check this post: Web UI shall be essentially the same. (mostly; but probably of some difference) Keep in mind that the IP allocation details are ISP specific: |
Beta Was this translation helpful? Give feedback.
-
|
Just had this issue today. |
Beta Was this translation helpful? Give feedback.
-
|
Had this issue today as well. Cannot do more than search request (linux, firefox via mobile data). |
Beta Was this translation helpful? Give feedback.
-
|
Same here. immediately blocked after click searching.. |
Beta Was this translation helpful? Give feedback.
and others
-
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