Docker Hub Rate Limit Checker
Check your Docker Hub pull limit. Browsers cannot read the registry rate-limit headers, so this gives you the exact CLI commands that can.
Docker Hub limits anonymous pulls to 100 per 6 hours per IP, and authenticated free accounts to 200. The real remaining count lives in ratelimit-remaining headers from registry-1.docker.io, which require an auth token and are CORS-blocked in the browser. This tool explains the limits and hands you the precise curl commands to check your real number.
The limits, plainly
- Anonymous (no login): 100 pulls per 6 hours, counted per source IP.
- Authenticated free account: 200 pulls per 6 hours.
- Pro/Team/Business plans: higher or unmetered pull allowances.
Why the in-browser check fails (honestly)
Reading ratelimit-remaining means getting a token from auth.docker.io and sending an authorized HEAD to registry-1.docker.io. The registry does not send CORS headers, so a web page cannot read the response. The tool attempts the fetch and, when it is blocked, surfaces the CLI commands instead of pretending with a fake number.
Stop hitting anonymous limits
Latchkey managed runners can authenticate to Docker Hub and cache pulled layers, so shared CI IPs do not burn through the anonymous 100-pull window and stall your builds with toomanyrequests.