Observed topology

AS16857 CENTEX

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16857: 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
AS46849	TEXAS LONE STAR NETWORK, LLC	Unclassified	IPv4	772
AS3356	Level 3 Parent, LLC	Transit	IPv4	692
AS13876	FiberLight, LLC	Unclassified	IPv4	164
AS20058	Totelcom Communications, LLC	Unclassified	IPv4	105
AS1299	Arelion Sweden AB	Transit	IPv4	96

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS36658	Angelo State University	Unclassified	IPv4	275

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS46849	TEXAS LONE STAR NETWORK, LLC	Unclassified	IPv4	1,055
AS3356	Level 3 Parent, LLC	Transit	IPv4	692
AS36658	Angelo State University	Unclassified	IPv4	275
AS13876	FiberLight, LLC	Unclassified	IPv4	274
AS18618	west central wireless	Unclassified	IPv4	118
AS20058	Totelcom Communications, LLC	Unclassified	IPv4	105
AS1299	Arelion Sweden AB	Transit	IPv4	96

Provenance

Where this comes from

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