Documentation

Main investigation entry point. Paste an ASN, AS-SET, prefix, IP, or domain.

1. Enter a query such as AS13335, AS-CLOUDFLARE, 1.1.1.0/24, 1.1.1.1, or example.com.
2. Results show origin/neighbours, RPKI, abuse contacts, explanations, and next-step actions.
3. From a result you can open Connectivity, Path Observations, IRR vs live, or hand off to Route Validator.
4. Recent searches are stored in your browser only.

Check whether a prefix is allowed to be advertised for an ASN/AS-SET (IRR + RPKI).

1. Single mode: enter a prefix; ASN/AS-SET is optional (origin can be resolved from the prefix).
2. Bulk mode: paste many prefixes and one ASN/AS-SET — green = covered, red = not covered.
3. From investigation results, use the prefill chips to jump here with prefix or object filled.
4. From Coverage, “Open in Route Validator” prefills the missing prefixes in bulk; you still enter the ASN/AS-SET.

Collapse a list of prefixes into the minimal covering set.

1. Paste one prefix per line (comments with # or ; are ignored).
2. Adjacent and nested ranges are summarized (e.g. two /25s → one /24).
3. IPv4 and IPv6 are handled separately.
4. Copy the output when you need a shorter customer prefix-list.

Turn prefixes into vendor CLI (Cisco, Juniper, FRR, BIRD, Arista, and others).

1. Paste prefixes, pick a vendor, set the list name and sequence settings.
2. Optional summarize before generate.
3. FRR/Cisco IOS add le 24 for IPv4 aggregates broader than /24.
4. Can be seeded from Route Validator bulk “covered” results or IRR compare handoff.

Compare a customer’s existing prefix-list to newly requested prefixes and show what is still missing.

1. Paste the existing list (vendor CLI or bare CIDRs) — only permit CIDRs count for coverage.
2. Deny lines (including trailing deny any / 0.0.0.0/0) are ignored so they do not mark everything as covered.
3. Paste the requested prefixes.
4. Already covered (green) is shown first; Missing (red) only appears when something is not covered; parse notes appear below.
5. Already covered = exact match or more-specific under an existing permit aggregate.
6. If a requested less-specific sits above existing more-specifics, it stays missing and those more-specifics are listed separately.
7. Use “Open in Route Validator” to validate the missing list against an ASN/AS-SET.

Compare two ASNs, AS-SETs, or prefix sets and show only-A / only-B / shared.

1. Choose the kind (ASN, AS-SET, or prefix).
2. Enter side A and side B.
3. Review the sets: only in A, only in B, and shared counts.
4. Useful for customer migrations, AS-SET membership changes, and IRR cleanup.