asn.dev

Observed topology

AS203729 IGLOO22225 igloo22225

Unclassified ARIN

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS203729: 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 IPv6149
AS55207June SlaterUnclassifiedIPv483
AS200365Possibly Lizards LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv64
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv64
AS202365Omer GOLGELIUnclassifiedIPv43
AS52025ParadoxNetworks LimitedUnclassifiedIPv42
AS212508Lowhosting services of Davide GennariUnclassifiedIPv42
AS5405Inter.link GmbHUnclassifiedIPv41
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401297June SlaterUnclassifiedIPv629

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6178
AS55207June SlaterUnclassifiedIPv483
AS401297June SlaterUnclassifiedIPv629
AS200365Possibly Lizards LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv64
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv64
AS202365Omer GOLGELIUnclassifiedIPv43
AS52025ParadoxNetworks LimitedUnclassifiedIPv42
AS212508Lowhosting services of Davide GennariUnclassifiedIPv42
AS5405Inter.link GmbHUnclassifiedIPv41

Provenance

Where this comes from

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