Observed topology

AS20645 PUREPEAK-ASN PurePeak Ltd.

Unclassified RIPE

Upstreams 8 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20645: 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
AS12400	Partner Communications Ltd.	Unclassified	IPv4 IPv6	2,728
AS1299	Arelion Sweden AB	Transit	IPv4	354
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	119
AS174	Cogent Communications, LLC	Transit	IPv4	114
AS1680	Cellcom Fixed Line Communication L.P	Mobile	IPv4	107
AS8551	Bezeq International Ltd.	Unclassified	IPv4	59
AS6453	TATA COMMUNICATIONS (AMERICA) INC	Transit	IPv6	33
AS3257	GTT Communications Inc.	Transit	IPv4	1

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12400	Partner Communications Ltd.	Unclassified	IPv4 IPv6	2,728
AS1299	Arelion Sweden AB	Transit	IPv4	354
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	119
AS174	Cogent Communications, LLC	Transit	IPv4	114
AS1680	Cellcom Fixed Line Communication L.P	Mobile	IPv4	107
AS8551	Bezeq International Ltd.	Unclassified	IPv4	59
AS6453	TATA COMMUNICATIONS (AMERICA) INC	Transit	IPv6	33
AS3257	GTT Communications Inc.	Transit	IPv4	1

Provenance

Where this comes from

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