Observed topology

AS26512 BMSL-2-ARIN

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

Upstream graph Who carries AS26512, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS26512 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26512: 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.

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	552
AS174	Cogent Communications, LLC	Transit	IPv4	397
AS6939	Hurricane Electric LLC	Transit	IPv4	330
AS3257	GTT Communications Inc.	Transit	IPv4	80

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS397325	Data Canopy Colocation, LLC	Unclassified	IPv4	696
AS40632	Fidelity & Guaranty Life	Unclassified	IPv4	123
AS17336	General Dynamics	Unclassified	IPv4	82
AS397338	Exostar LLC	Unclassified	IPv4	65
AS393267	American Type Culture Collection	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	1,344
AS397325	Data Canopy Colocation, LLC	Unclassified	IPv4	1,102
AS174	Cogent Communications, LLC	Transit	IPv4	931
AS6939	Hurricane Electric LLC	Transit	IPv4	423
AS40632	Fidelity & Guaranty Life	Unclassified	IPv4	123
AS3257	GTT Communications Inc.	Transit	IPv4	91
AS17336	General Dynamics	Unclassified	IPv4	82
AS397338	Exostar LLC	Unclassified	IPv4	65
AS393267	American Type Culture Collection	Unclassified	IPv4	58

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.