BGPKIT Labs / Archive Health Live
loading…

Archive Health

What the BGPKIT MRT archive is doing right now: which RouteViews and RIPE RIS collectors published a file in the last 24 hours, which went quiet, and which alert episodes are open. Every number below is read from the public v4 API when this page loads, with no build step and no stored copy.

loading…

Status signals

The API's own verdicts per data product: what each signal last observed, how old that is, and whether its freshness rule calls it stale. overall summarises the self signals; upstream covers the remote archives. Below that, dataset freshness from the storage layer.

Dataset freshness

Open and recovering alerts

Alert episodes that are open or recovering now, one row per condition and collector. Age is wall-clock time since onset. An episode is a derived condition on the file index, not a BGP event.

Alert history, last 72 hours

Collectors inside an alert in each hourly bucket, split by project and stacked by severity: critical at the base, warning above it. One row per project, shared vertical scale.

critical warning hover a bucket for its counts

Collector coverage

RIB coverage per collector, quietest first: hours since the newest RIB snapshot, days of snapshots kept in the ledger, and rows stored. Rows older than 24 hours are highlighted.

Method & limits

This page has no build step and no data pipeline of its own. Each panel fetches the public v4 API at request time; nothing is baked into the HTML. A number that looks wrong is an API or source problem, not a stale build: reload, then compare against the endpoint named under each panel.

Data sources: RouteViews and RIPE RIS, indexed by the BGPKIT broker. BGPKIT is not affiliated with the collectors. Corrections: contact@bgpkit.com.