Observed topology

AS20135 MTL-19 - Millennium Telcom LLC

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20135: 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
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	2,018
AS6939	Hurricane Electric LLC	Transit	IPv4	524
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	119
AS5056	Aureon Network Services	Residential	IPv4	27
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	21

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS65101	unnamed	Unclassified	IPv4	7
AS33589	City of Southlake	Unclassified	IPv4	3
AS65001	unnamed	Unclassified	IPv4	3
AS65003	unnamed	Unclassified	IPv4	3
AS65002	AS65002	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	2,019
AS6939	Hurricane Electric LLC	Transit	IPv4	539
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	121
AS5056	Aureon Network Services	Residential	IPv4	27
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	21
AS65101	unnamed	Unclassified	IPv4	7
AS33589	City of Southlake	Unclassified	IPv4	3
AS65001	unnamed	Unclassified	IPv4	3
AS65003	unnamed	Unclassified	IPv4	3
AS65002	AS65002	Unclassified	IPv4	2

Provenance

Where this comes from

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