Repository mirroring at carrier scale.
MirrorHub mirrors the open-source supply chain — Linux distributions, language package registries and container images — and serves it from edge nodes peered at the major European internet exchanges. Enterprises use the same network for private, access-controlled repositories and pipeline caches.
What runs on the network
Upstream mirrors
Full mirrors of Debian, Ubuntu, Alpine, Fedora and their security archives, refreshed every 5 minutes from the primary origin servers. Mirror list
Package registries
Pull-through proxies for PyPI, the npm registry, Docker Hub, GitHub Container Registry and Go module proxies, with content-addressed caching and per-object TTL.
Private mirrors
Customer-scoped namespaces for internal artifacts, vendor repositories and base images, served over authenticated HTTPS and filtered by source IP or token. See plans
Built for build machines
A large part of the traffic on this network is generated by continuous integration: thousands of pipelines pulling base images, language toolchains and dependency trees every hour. MirrorHub keeps that traffic on-net, close to the build fleet, so sections complete in seconds rather than minutes.
Predictable latency
Nodes sit inside carrier-neutral data centres in Frankfurt, Amsterdam, Warsaw and Stockholm, all directly connected to the exchanges that carry the upstream content. Median time-to-first-byte for a cached object is 11 ms from within the EU.
Zero-configuration fallback
Every mirror answers on standard paths that existing tooling already understands — apt, apk, dnf, pip, npm, docker, go. Change one URL and the pipeline keeps working.
Transparent by default
Live node health, synchronisation age and per-node throughput are published at status.mirrorhub.space. Nobody has to guess whether a mirror is stale before a release build.