Inspect originated IPv4 and IPv6 routes without confusing them with allocations or networks reached through transit.
Choose the AS number and address family
Use ASN Lookup, or start with AS13335. Select IPv4 and IPv6 separately. The list describes origins observed in selected snapshots; its source and date are part of the answer.
Three different lists
An originated prefix ends at that AS in the usable path evidence. An allocation is a registry resource. A route learned through a transit provider can describe a destination originated somewhere else. These sets need not match, so a transit AS’s customer reachability must not be relabelled as its own originated space.
Export with context
Select the address family before using TXT, CSV or JSON export. TXT provides a convenient prefix list; CSV and JSON retain source and observation fields. If the same prefix appears from two collectors, those are two observations rather than twice the address space. Keep the export timestamp and source details with an incident record.
A useful comparison
Suppose a previously saved export contains a /24 that is absent from today’s selected snapshots. Open that prefix in Prefix Lookup and inspect covering routes, other collectors and the observation times. A changed collector session can remove evidence without proving a worldwide withdrawal. Likewise, counting nested prefixes independently overstates unique address coverage; the ASN summary collapses overlaps within each address family.