Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Docker Hub has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for Docker Hub. The baseline covers six-hour pull allowance, private repositories, pull versus abuse throttling. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| six-hour pull allowancePaid plans have unlimited pulls subject to fair use. | Unauthenticated: 100 per IPv4/IPv6 subnet; Personal: 200 | Unauthenticated and Personal | DockerAug 22, 2026 |
| private repositoriesThe plan can host public repositories separately from the private-repository count. | 1 private repository | Personal | DockerAug 22, 2026 |
| 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 |
Tracked constraints and impact
Image pull allowances, authentication scope, private repository, and 429 behavior. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Docker Hub Pull Rate Limits
Docker Hub Pull Rate Limits, verified against Docker Hub's official documentation with scope, implementation impact, caveats, and a direct check.
Docker Hub Personal Private Repository Limit
Docker Hub Personal Private Repository Limit, verified against Docker Hub's official documentation with scope, implementation impact, caveats, and a direct check.
Docker Hub Rate-Limit Scope & 429 Messages
Docker Hub Rate-Limit Scope & 429 Messages, verified against Docker Hub's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Docker Hub baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Authenticated and unauthenticated pull allowances
Pull-rate and abuse-rate 429 messages