Observed topology

AS12097 MASSCOM

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12097: 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	1,234
AS27364	Armstrong	Residential	IPv4 IPv6	269
AS4922	Shenandoah Cable Television LLC	Residential	IPv4	61

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS18571	The Western Reserve Mutual Casualty Company	Unclassified	IPv4	59
AS400141	Pattersonville Telephone Co	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	1,278
AS27364	Armstrong	Residential	IPv4 IPv6	335
AS4922	Shenandoah Cable Television LLC	Residential	IPv4	68
AS18571	The Western Reserve Mutual Casualty Company	Unclassified	IPv4	59
AS400141	Pattersonville Telephone Co	Unclassified	IPv4	58

Provenance

Where this comes from

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