Observed topology

AS55009 ROUTER12

Residential ARIN Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55009: 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	172
AS10242	US Internet Corp	Residential	IPv4	61
AS5056	Aureon Network Services	Residential	IPv4	31

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS393846	Router12 Networks LLC	Unclassified	IPv4	132
AS400132	Reinbeck Telecommunications Utility	Unclassified	IPv4	81
AS14814	V.S. Enterprises LTD	Unclassified	IPv4	70
AS400080	Grundy Center Municipal Utilities	Unclassified	IPv4	36

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	475
AS393846	Router12 Networks LLC	Unclassified	IPv4	132
AS400132	Reinbeck Telecommunications Utility	Unclassified	IPv4	81
AS10242	US Internet Corp	Residential	IPv4	77
AS14814	V.S. Enterprises LTD	Unclassified	IPv4	70
AS400080	Grundy Center Municipal Utilities	Unclassified	IPv4	36
AS5056	Aureon Network Services	Residential	IPv4	31

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.