Observed topology

AS17143 WINNTELECOM

Residential ARIN Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17143: 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
AS12129	123.Net, Inc.	Hosting	IPv4 IPv6	495
AS46208	Peninsula Fiber Network, LLC	Unclassified	IPv4 IPv6	52
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	8

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS33539	ISP Management, Inc.	Unclassified	IPv4	232
AS62968	Central Michigan Communication, Co.	Unclassified	IPv4	10
AS63083	Chapin Long Distance, Inc.	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12129	123.Net, Inc.	Hosting	IPv4 IPv6	645
AS33539	ISP Management, Inc.	Unclassified	IPv4	232
AS46208	Peninsula Fiber Network, LLC	Unclassified	IPv4 IPv6	142
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	12
AS62968	Central Michigan Communication, Co.	Unclassified	IPv4	10
AS63083	Chapin Long Distance, Inc.	Unclassified	IPv4	2

Provenance

Where this comes from

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