Crankdat
Green Velvet presents LALALAND | Oasis Pool Party
Goldrush: Midnight Riders 2026
Le Youth
Getter | Clockwise 360 Experience
DUSK Music Festival 2025
Effin
AYYBO
Danny Avila
GRiZ Returns With New Single, 'BBFL'
International Discovery Series: Piezo (Italy)
ZHU On The Move: Why ZHU at Mesa Amphitheatre Is a Show You Cannot Miss
Miss Monique & Kapuchon Drop New 'Hot Sauce' Collab
REZZ Returns With 'A Shift In Perspective'
Capozzi
ISOxo
Bella Renee
YetepFor unauthenticated (anonymous) users, GitHub enforces a primary rate limit of for most API interactions, including repository downloads and clones via HTTPS. This limit is designed to prevent infrastructure abuse and is strictly monitored for operations like cloning over HTTPS or accessing files via raw.githubusercontent.com . Core GitHub Anonymous Rate Limits (2026) Unauthenticated (Anonymous) Limit Authenticated (User/Token) Limit REST API Requests 60 per hour per IP 5,000 per hour per user HTTPS Clones/Reads 15 operations per second (recommended) Subject to user limits Git LFS Downloads 300 requests per minute 3,000 requests per minute Git LFS Objects 30,000 objects per minute 300,000 objects per minute Key Factors Affecting Anonymous Downloads 1. IP-Based Tracking
Anonymous requests are tied to your , not an account. This is particularly problematic for users in offices or behind Carrier-Grade NAT (CGNAT) , as hundreds of people might share a single IP and exhaust the 60-request quota collectively in minutes. 2. Secondary Rate Limits github anonymous download limit
Even if you are under the 60-request hourly limit, you may hit if you: Make more than 100 concurrent requests . Consume excessive CPU resources in a short window. IP-Based Tracking Anonymous requests are tied to your