asn.dev

Observed topology

AS14135 NAVISITE-EAST-2

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14135: 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
AS7843Charter Communications IncResidentialIPv4 IPv61,059
AS3356Level 3 Parent, LLCTransitIPv4 IPv6863
AS6461Zayo BandwidthTransitIPv4118
AS174Cogent Communications, LLCTransitIPv431

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36020The Weather CompanyUnclassifiedIPv4180
AS394566ALEGEUS TECHNOLOGIES, LLCUnclassifiedIPv4 IPv694
AS14134Navisite Opco LLCUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7843Charter Communications IncResidentialIPv4 IPv61,229
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,022
AS36020The Weather CompanyUnclassifiedIPv4180
AS6461Zayo BandwidthTransitIPv4118
AS394566ALEGEUS TECHNOLOGIES, LLCUnclassifiedIPv4 IPv694
AS14134Navisite Opco LLCUnclassifiedIPv460
AS174Cogent Communications, LLCTransitIPv436

Provenance

Where this comes from

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