asn.dev

Observed topology

AS26134 BROAD-RUN-BORDER-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26134: 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 IPv61,112
AS3356Level 3 Parent, LLCTransitIPv4 IPv6671
AS2914NTT America, Inc.TransitIPv4 IPv6470

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7342VeriSign Infrastructure & OperationsUnclassifiedIPv4 IPv6155
AS16838VeriSign Infrastructure & OperationsUnclassifiedIPv4122
AS30060VeriSign Infrastructure & OperationsUnclassifiedIPv67

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,212
AS3356Level 3 Parent, LLCTransitIPv4 IPv6742
AS2914NTT America, Inc.TransitIPv4 IPv6515
AS7342VeriSign Infrastructure & OperationsUnclassifiedIPv4 IPv6155
AS16838VeriSign Infrastructure & OperationsUnclassifiedIPv4122
AS32787Akamai Technologies, Inc.HostingIPv461
AS11840VeriSign Infrastructure & OperationsUnclassifiedIPv67
AS30060VeriSign Infrastructure & OperationsUnclassifiedIPv67

Provenance

Where this comes from

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