your network
looking up your address…
ip
asn
prefix
rpki
lookup failed
BGPKIT Labs
Tools for the questions operators actually ask, answered from public routing data.
Every page here is a different way into the same corpus: MRT files from RouteViews and RIPE RIS, the RPKI repository history, and the visibility observed at route collectors. Each one states its window, its denominator, and what it cannot establish.
Look up and trace
One object at a time: what the routing system says about it now, and what changed.
- Lookupopen →
What is this ASN, prefix or IP, and what is attached to it?
Identity, centrality, ASPA, ROA coverage, and every origin seen for a prefix with the peer observations behind it.
- Timelineopen →
What happened to this prefix or ASN while I was not looking?
ROA object observations for one object, first and last seen, on one UTC axis with an event density strip over the window.
RPKI and ROV
Decisions before an announcement, and the consequences of enforcing validation.
- Preflightopen →
If I announce this prefix, will ROV networks drop it?
Five checks with evidence: ROA coverage, the RPKI validation verdict, origin consistency, IRR presence, ASPA.
- ROV Propagationnewopen →
Which ASes are forwarding RPKI-invalid routes?
Daily per-AS count of networks seen carrying at least one invalid (prefix, origin) route, with 10/100-route support tiers.
- ROV Checkopen →
How much of the Internet filters RPKI-invalid routes from this AS?
Routing cone, BGP connectivity and validation mix, plus the APNIC measurement share of vantage points that drop invalid routes.
- RPKI Trackeropen →
How is ROA and ASPA deployment moving?
Weekly observations across the public RPKI tree: deltas, regional breakdown, movers, full archive.
Data and collectors
The corpus underneath every other page here.
- Spectrumopen →
What is actually inside the MRT archive?
File-level coverage, volume, attribute mix, RPKI verdicts and parse cost for RouteViews and RIPE RIS.
- Broker statusopen →
Which collectors are still producing files, and which are not?
The BGPKIT Broker fleet view: catalog versus processed files, element volume, newest files.
In the browser
Parsing and inspection without a server round trip.
- MRT Exploreropen →
What is in this MRT file?
Opens an MRT file in the browser and walks its records, parsed by bgpkit-parser compiled to WebAssembly.
- wirescopeopen →
What does this BGP message look like on the wire?
A Wireshark-style dissector with byte spans, an editable hex view and RFC 7606 validation warnings.
The toolkit underneath
Labs projects are built on the open-source BGPKIT crates and CLIs.
- MonocleCLISearch, parse and inspect BGP data from public archives.
- BGPKIT ParserLibrary + CLI + WASMMRT, BGP and BMP parsing in Rust, with Python and WASM bindings.
- BGPKIT BrokerLibrary + CLI + serviceDiscover archive files by time, collector and type.
- BGPKIT CommonsLibraryShared utilities: bogons, AS metadata, country lookups.
Use the data directly
The pages here are thin clients over a public API. No key, no quota page.
REST APIapi.bgpkit.comBroker, utility and RPKI endpoints; documented with OpenAPI.
PythonpybgpkitClient for the broker and parser, on PyPI.
Rustbgpkit-parserThe parser behind every page on this site, on crates.io.
About
Labs is where BGPKIT tries interfaces before they become products. Projects may change shape or disappear. Nothing here reports traffic, and a collector observation is never the global routing table.