asn.dev

Observed topology

AS302 BCM-INFO-NET-AS

Unclassified ARIN Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS302: 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
AS6461Zayo BandwidthTransitIPv4 IPv6253
AS1299Arelion Sweden ABTransitIPv4 IPv6210
AS2914NTT America, Inc.TransitIPv4 IPv6141
AS4557Rice UniversityEducationIPv4 IPv6125

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8Rice UniversityUnclassifiedIPv4 IPv6672
AS7276University of HoustonEducationIPv4 IPv6291
AS13435Community Health Choice, Inc.UnclassifiedIPv4171
AS23218Texas Medical CenterUnclassifiedIPv4120
AS33563The Methodist HospitalUnclassifiedIPv4120
AS46298Harris County Hospital DistrictUnclassifiedIPv458
AS11015Texas Children's HospitalUnclassifiedIPv426

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6867
AS1299Arelion Sweden ABTransitIPv4 IPv6739
AS8Rice UniversityUnclassifiedIPv4 IPv6721
AS2914NTT America, Inc.TransitIPv4 IPv6467
AS7276University of HoustonEducationIPv4 IPv6291
AS13435Community Health Choice, Inc.UnclassifiedIPv4171
AS4557Rice UniversityEducationIPv4 IPv6163
AS23218Texas Medical CenterUnclassifiedIPv4120
AS33563The Methodist HospitalUnclassifiedIPv4120
AS46298Harris County Hospital DistrictUnclassifiedIPv458

All 11 adjacent →

Provenance

Where this comes from

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