asn.dev

Observed topology

AS395226 SACRAMENTO-COE

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395226: 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
AS2152CENICUnclassifiedIPv4 IPv62,143

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397909Elk Grove Unified School DistrictUnclassifiedIPv4548
AS3734Santa Clara County Office of EducationEducationIPv463
AS33235San Juan Unified School DistrictUnclassifiedIPv463
AS398396Natomas Unified School DistrictUnclassifiedIPv463
AS63398Twin Rivers Unified School DistrictUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2152CENICUnclassifiedIPv4 IPv62,912
AS397909Elk Grove Unified School DistrictUnclassifiedIPv4548
AS3734Santa Clara County Office of EducationEducationIPv463
AS33235San Juan Unified School DistrictUnclassifiedIPv463
AS398396Natomas Unified School DistrictUnclassifiedIPv463
AS63398Twin Rivers Unified School DistrictUnclassifiedIPv432

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.