Cheatography
https://cheatography.com
A handy guide to the various rate limits a user might come across when deploying their own self-hosted GitHub Actions Runners.
This is a draft cheat sheet. It is a work in progress and is not finished yet.
GitHub APIs
API requests to GitHub from self hosted runners |
1000 requests per hour across all actions within a repo |
Primary rate limit for authenticated users |
5,000 requests per hour |
Primary rate limit for GitHub App installations |
Min. 5,000 requests per hour (can go upto 12,500 depending upon the number of repos and users).
15,000 per hour if the installation is on a GitHub Enterprise Cloud Organization |
Primary rate limit for GITHUB_TOKEN in GitHub Actions |
1,000 requests per hour per repository.
For GitHub Enterprise Cloud Account, the limit is 15,000 requests per hour per repo |
Secondary Rate Limits:
Along with the primary rate limits noted above, GitHub also enforces some secondary rate limits.
- No more than 100 concurrent requests allowed.
- No more than 900 read requests per minute or 180 write requests per minute to a single REST endpoint.
|
Cloud Providers (Creating Runners)
AWS EC2 |
Uses Token Bucket system. Maximum of 1000 tokens, with a refill rate of 2 tokens per second. |
Google Cloud Engine |
1500 requests per minute per region |
Microsoft Azure |
1200 writes per hour per subscription |
Hetzner Cloud |
3600 requests per hour per project |
Package Registries
RubyGems Rate Limit |
10 requests per second |
|
|
Docker Hub
Anonymous Users |
100 pulls per 6 hours per IP address |
Authenticated Users |
200 pulls per 6 hour period per account |
Users with Paid Docker Subscription |
Up to 5000 pulls per day |
Image Registries
Amazon ECR |
Authenticated: 10 image pulls per second
Unauthenticated: 1 image pull per second |
Google Artifact Registry |
1000 requests per second. 300 write requests per second. |
Azure Container Registry (Basic Tier) |
1000 read, 100 write operations per minute |
|
