Observed topology

AS11598 RECOL-CT

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11598: 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
AS22742	Connecticut Education Network	Unclassified	IPv4 IPv6	125
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4 IPv6	113
AS5650	Frontier Communications of America, Inc.	Residential	IPv4 IPv6	91
AS7015	Comcast Cable Communications, LLC	Residential	IPv4	63

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS6062	NETPLEX	Unclassified	IPv4 IPv6	686
AS46651	Optimized Micro Devices LLC	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6062	NETPLEX	Unclassified	IPv4 IPv6	865
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4 IPv6	408
AS22742	Connecticut Education Network	Unclassified	IPv4 IPv6	379
AS5650	Frontier Communications of America, Inc.	Residential	IPv4 IPv6	300
AS7015	Comcast Cable Communications, LLC	Residential	IPv4 IPv6	228
AS46651	Optimized Micro Devices LLC	Unclassified	IPv4	58

Provenance

Where this comes from

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