asn.dev

Observed topology

AS202020 FLEXGRID

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202020: 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
AS174Cogent Communications, LLCTransitIPv4252
AS39326Syntura Group LimitedHostingIPv4153
AS6939Hurricane Electric LLCTransitIPv472
AS24482SG.GSHostingIPv49
AS37100SEACOM LimitedUnclassifiedIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS48185team.blue NVUnclassifiedIPv49
AS50300CustodianDC LimitedUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202241Business Design Centre LtdUnclassifiedIPv451

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4271
AS39326Syntura Group LimitedHostingIPv4173
AS6939Hurricane Electric LLCTransitIPv480
AS202241Business Design Centre LtdUnclassifiedIPv451
AS24482SG.GSHostingIPv410
AS37100SEACOM LimitedUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS50300CustodianDC LimitedUnclassifiedIPv410
AS48185team.blue NVUnclassifiedIPv49

Provenance

Where this comes from

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