Observed topology

AS44522 RIPN-RU-PRG

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44522: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	57
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	21
AS6939	Hurricane Electric LLC	Transit	IPv4	9
AS1764	Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH	Unclassified	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1
AS29504	Freenet Liberec, z.s.	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42385	Join-stock company "Internet Exchange"MSK-IX"	Unclassified	IPv4 IPv6	30

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	64
AS42385	Join-stock company "Internet Exchange"MSK-IX"	Unclassified	IPv4 IPv6	30
AS3257	GTT Communications Inc.	Transit	IPv4 IPv6	26
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	21
AS29504	Freenet Liberec, z.s.	Unclassified	IPv4 IPv6	6
AS24482	SG.GS	Hosting	IPv4 IPv6	2
AS1764	Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH	Unclassified	IPv4	1

Provenance

Where this comes from

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