Network status

Edge health for the delivery network behind this mirror. Latency figures are p50 over the trailing 30 days, measured from synthetic probes inside each region.

Edge regions

Frankfurt (eu-central) — origin-adjacent, full catalogue resident 12 ms p50

Paris (eu-west) — warm cache 19 ms p50

Stockholm (eu-north) — warm cache 24 ms p50

Madrid (eu-south) — warm cache 27 ms p50

Warsaw (eu-east) — single node until the second rack lands, elevated p99 33 ms p50

Fremont (us-west) — warm cache 41 ms p50

Tokyo (ap-northeast) — warm cache 52 ms p50

São Paulo (sa-east) — cold for tail versions, misses fall back to Frankfurt 88 ms p50

Aggregate figures

99.95%

edge uptime, 30 days

92.6%

cache hit ratio

21 ms

median TTFB, all regions

The hit ratio counts every path. Pinned /v/<version>/ requests alone sit at 98.1% — the misses are overwhelmingly first requests for tail versions in the two cold regions above.

Origin sync

Check	State
Upstream registry poll	every 5 min, last run 2026-09-19 06:12 UTC
Queue depth	0 packages pending extraction
Digest re-verification sweep	completed 2026-09-16, 63 of 63 versions matched

Recent incidents

Date	Region	Summary	Duration
2026-09-08	São Paulo	Transit provider reroute, p50 above 300 ms, requests shed to Frankfurt	1h 55m
2026-08-19	Warsaw	Node reboot after a kernel update, cache rebuilt cold on return	26m
2026-07-02	All regions	Extraction worker stalled on a malformed tarball; newly published releases reached the edge late, mirrored versions unaffected	3h 10m

None of the above touched already-mirrored /v/<version>/ paths: those are immutable objects served from edge storage and do not consult the origin, so an origin-side stall only delays releases that were not mirrored yet.