Observed topology

AS47236 CITYLINK-AS CityLink Ltd

Unclassified RIPE

Upstreams 14 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 15

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS47236: 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	1,707
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	953
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	486
AS31500	Global Network Management Inc	Unclassified	IPv4	63
AS6939	Hurricane Electric LLC	Transit	IPv4	51
AS8359	MTS PJSC	Mobile	IPv4	46
AS50509	Transroute Telecom LTD	Unclassified	IPv4	35
AS50673	Serverius Holding B.V.	Unclassified	IPv4	18
AS24482	SG.GS	Hosting	IPv4	14
AS37721	Virtual Technologies & Solutions	Residential	IPv4	14

All 14 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57856	MOU Lyceum N 1	Unclassified	IPv4	59
AS48354	CityLink Ltd	Unclassified	IPv4	3

Adjacency

Adjacent networks

All 15

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

AS	Network	Type	Families	Paths seen
AS31133	PJSC MegaFon	Mobile	IPv4	1,734
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	975
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	486
AS31500	Global Network Management Inc	Unclassified	IPv4	63
AS57856	MOU Lyceum N 1	Unclassified	IPv4	59
AS6939	Hurricane Electric LLC	Transit	IPv4	58
AS8359	MTS PJSC	Mobile	IPv4	46
AS50509	Transroute Telecom LTD	Unclassified	IPv4	35
AS50673	Serverius Holding B.V.	Unclassified	IPv4	19
AS24482	SG.GS	Hosting	IPv4	15

All 15 adjacent →

Provenance

Where this comes from

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