asn.dev

Observed topology

AS567 ASN-LNET-AS - Los Nettos

Unclassified APNIC

Upstreams 1 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 4
Upstream graph Who carries AS567, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS567 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS567: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS2152CENICUnclassifiedIPv463

Transit

Downstream networks

inferred

Networks for which AS567 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS4University of Southern CaliforniaUnclassifiedIPv4 IPv6959
AS47University of Southern CaliforniaUnclassifiedIPv4425
AS226Los NettosUnclassifiedIPv4 IPv6397
AS127Jet Propulsion LaboratoryUnclassifiedIPv4356
AS25789Loyola Marymount UniversityUnclassifiedIPv4154
AS3659Claremont University ConsortiumEducationIPv4 IPv649
AS14486Occidental CollegeUnclassifiedIPv426

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS567 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS2152CENICUnclassifiedIPv4 IPv63,424
AS226Los NettosUnclassifiedIPv4 IPv61,843
AS4University of Southern CaliforniaUnclassifiedIPv4 IPv6959
AS2153CENICUnclassifiedIPv4451
AS47University of Southern CaliforniaUnclassifiedIPv4425
AS127Jet Propulsion LaboratoryUnclassifiedIPv4356
AS25789Loyola Marymount UniversityUnclassifiedIPv4154
AS3659Claremont University ConsortiumEducationIPv4 IPv649
AS14486Occidental CollegeUnclassifiedIPv426

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.