Data Freshness
When each pipeline last ran, what changed, and how current the data is.
One or more pipelines look stale.
| Pipeline | Schedule | Last run | Last data change | Data through | Upstream | Status |
|---|---|---|---|---|---|---|
| cran-downloads | daily 07:00 UTC | 23h ago |
23h ago
4 shards changed last run
|
n/a | n/a | current |
| cran-feed | every 6 hours | 15h ago |
15h ago
|
n/a | n/a | slow |
| cran-metadata | daily 06:00 UTC | 1d ago |
1d ago
|
n/a | n/a | current |
| cran-queue | hourly | 12h ago |
12h ago
|
n/a | n/a | stale |
| data | daily 08:00 UTC | 12h ago |
12h ago
|
n/a | n/a | current |
| r2u-downloads | daily 06:00 UTC | 1d ago |
2d ago
no change last run
|
2026-06-01 |
in sync
source 27d ago
|
current |
"Last run" is the most recent pipeline execution; "last data change" is the most recent run that actually published new data. r2u downloads are raw, un-deduplicated apt request counts and lag their source by about a month.