Observed topology

AS11178 RS-ACCESSPL

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11178: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	979
AS3356	Level 3 Parent, LLC	Transit	IPv4	138
AS174	Cogent Communications, LLC	Transit	IPv4	71

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS22702	RingSquared	Residential	IPv4	2,207
AS7849	RingSquared CC	Unclassified	IPv4	181
AS32117	Berkshire Health Systems	Unclassified	IPv4	131
AS40944	Mass College of Liberal Arts	Unclassified	IPv4	120
AS395922	GCET	Unclassified	IPv4	95
AS32336	Springfield College	Unclassified	IPv4	43

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	3,100
AS22702	RingSquared	Residential	IPv4	2,213
AS3356	Level 3 Parent, LLC	Transit	IPv4	803
AS7849	RingSquared CC	Unclassified	IPv4	311
AS174	Cogent Communications, LLC	Transit	IPv4	198
AS32117	Berkshire Health Systems	Unclassified	IPv4	131
AS40944	Mass College of Liberal Arts	Unclassified	IPv4	120
AS395922	GCET	Unclassified	IPv4	95
AS32336	Springfield College	Unclassified	IPv4	43

Provenance

Where this comes from

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