Observed topology

AS42396 PPLNETUA-AS PJSC Telesystems of Ukraine

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42396: 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
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	1,055
AS35297	Dataline LLC	Unclassified	IPv4	828
AS35320	Eurotranstelecom Ltd	Unclassified	IPv4	239
AS6939	Hurricane Electric LLC	Transit	IPv4	138
AS9002	RETN Limited	Unclassified	IPv4	64
AS48845	Stargroup LLC	Unclassified	IPv4	60
AS24482	SG.GS	Hosting	IPv4	38

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56459	PE Golub Iryna Anatoliivna	Unclassified	IPv4	138
AS215765	"RADIO-LINK SMART" LLC	Unclassified	IPv4	49
AS39928	Broadcasting TV Company "Studio 1+1"	Unclassified	IPv4	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1820	WNET TELECOM USA Corp.	Residential	IPv4	1,124
AS35297	Dataline LLC	Unclassified	IPv4	1,003
AS35320	Eurotranstelecom Ltd	Unclassified	IPv4	257
AS6939	Hurricane Electric LLC	Transit	IPv4	138
AS56459	PE Golub Iryna Anatoliivna	Unclassified	IPv4	138
AS39928	Broadcasting TV Company "Studio 1+1"	Unclassified	IPv4	111
AS9002	RETN Limited	Unclassified	IPv4	98
AS48845	Stargroup LLC	Unclassified	IPv4	60
AS215765	"RADIO-LINK SMART" LLC	Unclassified	IPv4	49
AS24482	SG.GS	Hosting	IPv4	40

Provenance

Where this comes from

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