Observed topology

AS37406 RCS-Communication - RCS-Communication

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37406: 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
AS328605	MUYA FIBRE CONSTRUCTION LTD	Residential	IPv4	155
AS9129	MTN SA	Unclassified	IPv4	151
AS37100	SEACOM Limited	Unclassified	IPv4	125
AS6939	Hurricane Electric LLC	Transit	IPv4	109
AS327786	4G Telecom	Unclassified	IPv4	72
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	54
AS328977	Wavex Internet Service Provider LTD	Residential	IPv4	16

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS327786	4G Telecom	Unclassified	IPv4	47

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS328605	MUYA FIBRE CONSTRUCTION LTD	Residential	IPv4	155
AS9129	MTN SA	Unclassified	IPv4	151
AS37100	SEACOM Limited	Unclassified	IPv4	150
AS327786	4G Telecom	Unclassified	IPv4	119
AS6939	Hurricane Electric LLC	Transit	IPv4	109
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	76
AS328977	Wavex Internet Service Provider LTD	Residential	IPv4	16

Provenance

Where this comes from

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