ROOTBEER

Explore Internet2's peering topology and the routes seen across each session, refreshed daily.

Browse the networks whose LPP probe responses returned over R&E paths — sortable by prefix count and share of results over R&E, down to the probed addresses and their PTR records.

Probe the observed routing policy for any IPv4/IPv6 address, hostname, or IPv4 prefix — no traceroutes, just the answer.

Explore a full mesh of traceroutes between ~108 CAIDA Ark nodes hosted in R&E networks on a world map — select a node to see the ASes its paths traverse, how many AS hops away they are, and hop-level path detail in both directions.

Explore how anycast IPv4 prefixes are reached worldwide — RTT vs AS-hop count per vantage point, split by R&E vs commodity origin.

Compare CAIDA Ark traceroutes from default-route vs full-localpref R&E vantage points to a more-specific commodity prefix — an overlaid AS-level Sankey shows where default-route paths fail to reach.

Plan and validate RPKI ROAs for your prefixes.

Look up RIR registration and IP allocation hierarchy for any address or prefix.

Build and analyze IRR AS-SET objects for your customer cone.

Suggest RPKI-ASPA providers for your Autonomous System. Doesn't yet cover every case — provides a starting point, not a comprehensive plan.

Visualize RPKI ROA coverage across your routing footprint.

Visualize the deployed RPKI-ASPA topology of the Internet, with optional cross-validation against CAIDA's inferred AS relationships.

The set of origin ASes Internet2 (AS11537) tags as participants, aggregated from R&E BGP data.

For every BGP peer of AS11537: the IRR as-set it publishes (aut-num export, AS-ANY export or PeeringDB), expanded via ROOTBEER's IRRd and compared with the ASNs the peer actually announces — accepted, rejected, and never seen.

For testing ROOTBEER's own IRRd mirror, not a product: enter an AS number and see its aut-num object from every mirrored registry, plus the exact GraphQL query sent.