Observed topology

AS52000 MIRHOSTING

Hosting RIPE Content

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52000: 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
AS3257	GTT Communications Inc.	Transit	IPv4	9
AS1299	Arelion Sweden AB	Transit	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS153914	NETRANEX TECHNOLOGIES (INDIA) PRIVATE LIMITED	Unclassified	IPv4 IPv6	399
AS202423	Tyurin Viktor Mihaylovich	Unclassified	IPv4	8
AS30344	365.hosting	Unclassified	IPv4	4
AS216300	Closed Joint Stock Company "AbkhazMedia"	Unclassified	IPv4	2
AS206932	MIRhosting B.V.	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS153914	NETRANEX TECHNOLOGIES (INDIA) PRIVATE LIMITED	Unclassified	IPv4 IPv6	459
AS140641	YOTTA NETWORK SERVICES PRIVATE LIMITED	Unclassified	IPv4 IPv6	458
AS1299	Arelion Sweden AB	Transit	IPv4	16
AS3257	GTT Communications Inc.	Transit	IPv4	10
AS202423	Tyurin Viktor Mihaylovich	Unclassified	IPv4	8
AS30344	365.hosting	Unclassified	IPv4	4
AS216300	Closed Joint Stock Company "AbkhazMedia"	Unclassified	IPv4	2
AS35280	F5 Networks SARL	Hosting	IPv4	1
AS206932	MIRhosting B.V.	Unclassified	IPv4	1

Provenance

Where this comes from

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