Observed topology

AS13868 PEAK INTERNET

Residential ARIN

Upstreams 3 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13868: 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 IPv6	148
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	139
AS6939	Hurricane Electric LLC	Transit	IPv4	36

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS12044	Willamette Valley Internet	Unclassified	IPv4	186
AS53789	City of Lebanon	Unclassified	IPv4	55
AS397819	Consumers Power, Inc.	Unclassified	IPv4	44
AS397510	Consumers Power, Inc.	Unclassified	IPv4	43
AS10554	WESTERN UNIVERSITY OF HEALTH SCIENCES	Education	IPv4	17

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	310
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	254
AS12044	Willamette Valley Internet	Unclassified	IPv4	186
AS6939	Hurricane Electric LLC	Transit	IPv4	104
AS53789	City of Lebanon	Unclassified	IPv4	55
AS397819	Consumers Power, Inc.	Unclassified	IPv4	44
AS397510	Consumers Power, Inc.	Unclassified	IPv4	43
AS10554	WESTERN UNIVERSITY OF HEALTH SCIENCES	Education	IPv4	17

Provenance

Where this comes from

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