Observed topology

AS31195 MF-DV-AS

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 9 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31195: 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
AS31133	PJSC MegaFon	Mobile	IPv4 IPv6	5,112

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS34434	JSC Atlas-2	Unclassified	IPv4	951
AS49093	KGKU ITC Primorskogo kraya	Unclassified	IPv4	61
AS57637	Government of the Khabarovsk Krai	Unclassified	IPv4	37
AS47560	KIT-Magadan LLC	Unclassified	IPv4	30
AS48312	PJSC ALROSA	Unclassified	IPv4	12
AS47634	Udokan Copper LLC	Unclassified	IPv4	8
AS52166	Rusagro-Primorie LLC	Unclassified	IPv4	7
AS48058	Far-Eastern Distribution Company JSC.	Unclassified	IPv4	5
AS62143	FSUE RTRN	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS31133	PJSC MegaFon	Mobile	IPv4 IPv6	6,226
AS34434	JSC Atlas-2	Unclassified	IPv4	951
AS49093	KGKU ITC Primorskogo kraya	Unclassified	IPv4	61
AS57637	Government of the Khabarovsk Krai	Unclassified	IPv4	37
AS47560	KIT-Magadan LLC	Unclassified	IPv4	30
AS48312	PJSC ALROSA	Unclassified	IPv4	12
AS47634	Udokan Copper LLC	Unclassified	IPv4	8
AS52166	Rusagro-Primorie LLC	Unclassified	IPv4	7
AS48058	Far-Eastern Distribution Company JSC.	Unclassified	IPv4	5
AS62143	FSUE RTRN	Unclassified	IPv4	3

Provenance

Where this comes from

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