Observed topology

AS16832 SECOM-1

Residential ARIN Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16832: 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	298
AS3356	Level 3 Parent, LLC	Transit	IPv4	40
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	28

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS10821	The Pioneer Telephone Association, Inc.	Residential	IPv4	270
AS53903	Rebeltec Communications, LLC	Unclassified	IPv4	234
AS397075	SPANISH-PEAKS-REGIONAL-HEALTH-CENTER	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	798
AS10821	The Pioneer Telephone Association, Inc.	Residential	IPv4	270
AS53903	Rebeltec Communications, LLC	Unclassified	IPv4	234
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	93
AS397075	SPANISH-PEAKS-REGIONAL-HEALTH-CENTER	Unclassified	IPv4	61
AS3356	Level 3 Parent, LLC	Transit	IPv4	40

Provenance

Where this comes from

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