bgp.fyi / design study 03 dev.api.bgpkit.com / v4 / no key

atlas

— collectors, one view of what they actually deliver

The route collector fleet, treated as the product: who is in the catalog, who is still producing parsed files, and exactly where those two answers disagree. Read-only; every figure below is a live v4 dev API response.

collectors in catalog

—

collector catalog

with processed files

—

file processing index

parsed files · 24h

—

file processing index

parse failures · 24h

—

file processing index

median updates lag

…

file feed · loading

fleet strip

Coverage gap catalog vs processed files

waiting for responses

In catalog, no processed files

—

Processed, not in catalog

A name that appears in our processed-file records but not in the current collector catalog, usually a renamed collector.

—

No parsed file in 24h

—

—

Collectors

sorted by health (failing first), then name

waiting for responses