STATUS
Per-list health.
Each row below is one public list mikrotikfilters serves through /api/lists/<slug>.rsc. Theentries column is the count right now;last built is when the rendered.rsc snapshot was last refreshed in the edge cache; last 24h summarises ingest runs against the upstream feeds — successes, failures, and the net change in entries over the window.
No per-IP or per-subscriber metrics flow through this page. The lists themselves are public artefacts; this page surfaces ingestion-activity over them.
Loading list status…
Could not load status. Reload to retry.
| List | Category | Entries | Last checked | Last built | 24h ingest | 24h Δ entries |
|---|
- Last checked
- When the ingest pipeline last looked at this list's upstream feed, whatever the outcome. This is the liveness signal: it moves on every scheduled run even when nothing changed. If this is recent, the pipeline is running for this list. failed in red means the most recent run errored.
- Last built
- When the downloadable artefacts were last re-generated. This only moves when the content actually changed — a feed that is checked on schedule but hasn't changed keeps an old build timestamp and is still perfectly healthy. Compare it against Last checked rather than the wall clock; an old build date on its own is not a fault.
- 24h ingest
- How many times an upstream-feed fetch ran for this list in the last 24 hours. All ok means every run finished cleanly — including the fast-path where the upstream feed hadn't changed since the previous fetch (`If-None-Match` / `If-Modified-Since` short-circuit).N failed appears in red when any run returned a hard error. No runs means this list's ingest schedule is less frequent than daily — bogons refresh weekly and country lists monthly, so both sit at “no runs” most days. Check Last checked for the actual cadence; “no runs” is not a failure signal on its own.
- 24h Δ entries
- Net change in the entry count from ingest activity over the last 24 hours:
entries_added − entries_removedsummed across all runs. Zero is normal for stable feeds (Spamhaus is rarely active); positive when upstream added IPs; negative when entries expired or were purged. An entry that churned within the window (added then removed) nets to zero — the Entries column is the authoritative current count.