4 ms·
Your work is probably all exiting through the same IP, you competing with others on the same IP is causing the rate limit.
by colechristensen 7mo ago
Your work is probably all exiting through the same IP, you competing with others on the same IP is causing the rate limit.
- CupricTea 7mo agoI've considered this, but the company is small enough that the number of people who would be on GitHub at any moment (instead of our internal git forge) can be counted on one hand, and when I'm the first one there in the morning it still rate limits me.
- growse 7mo agoMaybe your company's ISP is CGNat'ting you?
- NewJazz 7mo agoDo you have any on-prem cicd jobs that access github? Our's kept failing, had to move over to the ECR release of some stuff.
- colechristensen 7mo agoHm, I've also noticed sites being more aggressive about verifications after I started using LLMs locally. They think I'm a bot (which... fair), even on completely unrelated sites I seem to be getting prompted for human verification much more often.
- embedding-shape 7mo agoThe very same thing happen on my residential connection, I can do one search query, then I'm rate limited for 15+ minutes, same if I access any list of commits.
- tyingq 7mo agoMay explain the ipv6 resistance. Hard to do effective per-ip rate-limiting with v6.
- nickserv 7mo agoI don't understand, wouldn't it make it easier?
- hkt 7mo agoNo, IPv6 as it is supposed to be implemented gives (say) a single server a /64, which is for all intents and purposes an inexhaustible supply of IPs. You could in principle have an IP per site you visit and have plenty left to spare. Random Google result with a bit more: https://www.captaindns.com/en/blog/ipv6-subnet-sizes-48-vs-56-vs-64 https://www.captaindns.com/en/blog/ipv6-subnet-sizes-48-vs-5... So if I wanted to annoy GitHub, I could connect to them without ever using the same IP twice. Their response would have to be banning my /64, or possibly /56.
- Hikikomori 7mo agoIts not harder to rate limit a /64 though.
- mmbleh 7mo agoIt is because the IPv6 rollout has not been consistent. Some assign /64 per machine, some assign /64 per data center. Some even go the other way and do a /56 per machine. We've had to build up a list of overrides to do some ranges by /64 and others by /128 because of how they allocate addresses. This creates extra burden on server operators and it's not surprising that some just choose not to deal with it.
- GoblinSlayer 7mo agoThis problem exists for ipv4 too: some machines have static address, others have dynamic, so you can implement overrides.
- tyingq 7mo agoIpv6 is cheap though. If I want to get past your IP or per Network limit, options abound.