Quick answer
Docker Hub documents pull versus abuse throttling as Separate pull-rate and abuse-rate controls. Docker documents distinct 429 response bodies for pull exhaustion and abuse throttling.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| pull versus abuse throttlingDocker documents distinct 429 response bodies for pull exhaustion and abuse throttling. | Separate pull-rate and abuse-rate controls | All users | DockerAug 22, 2026 |
Why does this limit matter?
Retrying an abuse throttle as if it were a six-hour pull reset can prolong an outage.
This value is scoped to All users; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read the full 429 response and rate-limit headers before deciding the retry policy.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- The abuse limit is intentionally not published as one numeric global threshold.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related