Observed topology

AS50427 ORIONNET-ABK

Residential RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50427: 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	753
AS31133	PJSC MegaFon	Mobile	IPv4	625
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	106
AS48858	JSC "ER-Telecom Holding"	Unclassified	IPv4	75
AS31257	Orion Telecom LLC	Residential	IPv6	34
AS13094	JSC "ER-Telecom Holding"	Unclassified	IPv4	26
AS43298	Storm Networks LLC	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS50022	Kristelecom Ltd.	Unclassified	IPv4	82

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12389	PJSC Rostelecom	Residential	IPv4	810
AS31133	PJSC MegaFon	Mobile	IPv4	643
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	106
AS50022	Kristelecom Ltd.	Unclassified	IPv4	89
AS48858	JSC "ER-Telecom Holding"	Unclassified	IPv4	76
AS31257	Orion Telecom LLC	Residential	IPv4 IPv6	47
AS13094	JSC "ER-Telecom Holding"	Unclassified	IPv4	26
AS43298	Storm Networks LLC	Unclassified	IPv4	1

Provenance

Where this comes from

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