Observed topology

AS34470 PTKOM-AS PortTelekom Autonomous system

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34470: 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
AS12389	PJSC Rostelecom	Residential	IPv4	360
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	136

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42537	AIT LLC	Unclassified	IPv4	53
AS197596	Declarant Plus LLC	Unclassified	IPv4	53
AS52069	Public Joint Stock Company "Commercial Port of Vladivostok"	Unclassified	IPv4	41
AS34352	MSN Telecom LLC	Unclassified	IPv4	27
AS41060	Public Joint-Stock Commercial Bank Primorye	Unclassified	IPv4	20
AS56845	V-Lazer Ltd.	Unclassified	IPv4	3
AS213933	Deltaleasing LLC	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4	517
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	179
AS42537	AIT LLC	Unclassified	IPv4	53
AS197596	Declarant Plus LLC	Unclassified	IPv4	53
AS52069	Public Joint Stock Company "Commercial Port of Vladivostok"	Unclassified	IPv4	41
AS34352	MSN Telecom LLC	Unclassified	IPv4	27
AS41060	Public Joint-Stock Commercial Bank Primorye	Unclassified	IPv4	20
AS56845	V-Lazer Ltd.	Unclassified	IPv4	3
AS213933	Deltaleasing LLC	Unclassified	IPv4	3

Provenance

Where this comes from

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