Status

Is it up, is it keeping up, is every ring healthy

Checking…

Service

Measured right now by the API: can it reach the index and the pool.

Pipeline checking

Whether the pool is being kept up to date: the syncs, the checks, the promotions.

Rings

Latest real-pacman check per ring and architecture, and when the ring last moved.

Ring	Arch	Health	Checked	Release	Moved	Databases

Sources

Last sync of every upstream repository. A source is late when its last sync is older than … hours (a long import of one source makes the others wait their turn).

Source	Arch	Last sync	Result	Upstream	In edge	Missing

Coverage

every source, every number

What upstream serves, what edge already pins, what stable pins. Superseded versions stay in the pool until retention runs, so the size can exceed the upstream's.

Source	Arch	Upstream	In edge	Missing	In stable	Progress	Size	Last sync

The pipeline, in numbers

Watch it run →

The pool's own jobs, pulled by workers with a per-job credential; a snapshot every 30 minutes records what ran and what is running now.

Pool growth 7 days

bytes stored once, from the metrics snapshots

Imports per day 14 days

packages brought into the pool by the sync runs

Health 14 days

worst result per day, per ring and architecture

Sync throughput last runs

MB/s per sync run, one worker each

Worker minutes per day

time the project's workers spent on pool jobs

Pool jobs 7 days

sync, promote, health, gc pulled by workers: done, failed, waiting

Factory builds 14 days

per day: contributors' builds staged, the project's published, failed

Job	Last	Runs 7d	Failed	Running	Minutes 7d

Incidents

Rollbacks, blocked gates and failed checks in the journal, newest first. An empty list is the goal.

Status	What	Ring	Summary	When