asn.dev

Observed topology

AS203062 ALEXANDRE-ROUX-ASRINFOPRO Alexandre Roux

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS203062: 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 LLCTransitIPv4 IPv6859
AS47160MOJI SASResidentialIPv4 IPv6106
AS2027MilkyWan AssociationResidentialIPv636
AS204092Association GRIFONUnclassifiedIPv4 IPv628
AS25091IP-Max SAUnclassifiedIPv623
AS214757Jakub KrsaUnclassifiedIPv611
AS34927iFog GmbHHostingIPv4 IPv69
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv44

All 17 upstreams →

Transit

Downstream networks

inferred

Networks for which AS203062 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 17

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6859
AS47160MOJI SASResidentialIPv4 IPv6106
AS2027MilkyWan AssociationResidentialIPv636
AS204092Association GRIFONUnclassifiedIPv4 IPv628
AS25091IP-Max SAUnclassifiedIPv623
AS214757Jakub KrsaUnclassifiedIPv611
AS34927iFog GmbHHostingIPv4 IPv69
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv44

All 17 adjacent →

Provenance

Where this comes from

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