Home / Status

Service status

Generated from the sync daemon every five minutes. All times UTC.

All systems operational. Last incident: 2026-09-18, a 42-minute interruption to rsync service during a storage migration. No data loss.
99.98%uptime, 90 days
1.9 TBserved today
37active connections
11 msmedian TTFB, EU

Synchronisation

Lag is the difference between upstream publish time and the moment the tree became available here.

Upstream Method Schedule Last run Lag Result
Debianrsyncevery 6 h15:126 minOK
Ubuntursyncevery 6 h15:0711 minOK
Alpine Linuxrsyncevery 2 h15:144 minOK
Arch Linuxrsyncevery 1 h15:153 minOK
Fedorarsyncevery 12 h15:0018 minRunning
CentOS Streamrsyncevery 8 h15:099 minOK
Kali Linuxrsyncevery 12 h14:5622 minOK
Linux Mintrsyncevery 6 h15:117 minOK
openSUSErsyncevery 6 h15:0315 minOK
PyPIbandersnatchevery 5 min15:135 minOK
npm registryreplicatecontinuous15:162 minOK
Go module proxyathensevery 30 min15:108 minOK

Incident history

Ninety days, newest first.

Date Duration Affected Summary
2026-09-18 42 min rsync Storage migration; rsync daemon stopped, HTTPS unaffected.
2026-08-02 9 min All services Upstream provider network maintenance.
2026-06-27 17 min HTTPS Certificate renewal misconfiguration; old certificate served.
2026-05-14 3 min PyPI bandersnatch worker restart loop after upstream index change.

How to read this page

Status is derived from the exit code of the last sync job plus a HEAD request against a known-good file in each tree. A green badge means the last run finished successfully and the sample file matched its expected checksum. Amber means a job is currently running — this is normal and not an error.

If you see a red badge that persists for more than one schedule interval, please let us know. We do not always notice upstream breakage on low-traffic mirrors.