Github Anonymous ~repack~ Download Limit Page

Downloading specific files anonymously also triggers platform-wide size restrictions: Rate limits for the REST API - GitHub Docs

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

Rapidly create content or access single endpoints (limited to 900 read points per minute). 3. Storage and File Size Caps Secondary Rate Limits Rapidly create content or access

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. Consume excessive CPU resources in a short window

For 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