asn.dev

Observed topology

AS202939 CHIMON-NETWORK Chimon Technology Ltd

Residential RIPE Cable/DSL/ISP

Upstreams 18 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 16
Upstream graph Who carries AS202939, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS202939 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS202939: 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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6245
AS44324MoeDove LLCResidentialIPv4 IPv6202
AS206069Cornseed LimitedResidentialIPv6105
AS27523Kawaii Networks LLCUnclassifiedIPv673
AS34927iFog GmbHHostingIPv670
AS31898Oracle CorporationHostingIPv664
AS17433Hytron Network Services LimitedResidentialIPv631
AS7720Skywolf Technology LLCUnclassifiedIPv628
AS51087Bling Network LtdUnclassifiedIPv620
AS24482SG.GSHostingIPv4 IPv614

All 18 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6245
AS44324MoeDove LLCResidentialIPv4 IPv6202
AS206069Cornseed LimitedResidentialIPv6105
AS27523Kawaii Networks LLCUnclassifiedIPv673
AS34927iFog GmbHHostingIPv670
AS31898Oracle CorporationHostingIPv664
AS17433Hytron Network Services LimitedResidentialIPv631
AS7720Skywolf Technology LLCUnclassifiedIPv628
AS51087Bling Network LtdUnclassifiedIPv620
AS24482SG.GSHostingIPv4 IPv614

All 18 adjacent →

Provenance

Where this comes from

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