Observed topology

AS34629 ORNRU-AS Kvant-telecom uplink:

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34629: 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
AS43727	JSC KVANT-TELEKOM	Residential	IPv4 IPv6	540

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS52197	Oblastnoe gosudarstvennoe uchrejdenie Centr Gosudarstvennyh Informacionnyh resursov Orlovskoy oblasti	Unclassified	IPv4	63
AS201778	FSBE Institution of HE "I.S. TURGENEV Orlovsky STATE UNIVERSITY"	Unclassified	IPv4	41
AS211714	BUZ Orlovskoy oblasti MIAC	Unclassified	IPv4	32
AS57434	Kompyuternaya Firma Bagira Ltd.	Unclassified	IPv4	24
AS49279	BEFL Ltd.	Unclassified	IPv4	11

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS43727	JSC KVANT-TELEKOM	Residential	IPv4 IPv6	711
AS52197	Oblastnoe gosudarstvennoe uchrejdenie Centr Gosudarstvennyh Informacionnyh resursov Orlovskoy oblasti	Unclassified	IPv4	63
AS201778	FSBE Institution of HE "I.S. TURGENEV Orlovsky STATE UNIVERSITY"	Unclassified	IPv4	41
AS211714	BUZ Orlovskoy oblasti MIAC	Unclassified	IPv4	32
AS57434	Kompyuternaya Firma Bagira Ltd.	Unclassified	IPv4	24
AS49279	BEFL Ltd.	Unclassified	IPv4	11

Provenance

Where this comes from

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