asn.dev

Observed topology

AS201119 ICEWOOD Icewood LLC

Hosting RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS201119: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4144
AS31500Global Network Management IncUnclassifiedIPv4 IPv694
AS50673Serverius Holding B.V.UnclassifiedIPv474
AS41095IPTP LTDHostingIPv460
AS20764CJSC RASCOMUnclassifiedIPv4 IPv652
AS1299Arelion Sweden ABTransitIPv438
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv630
AS6939Hurricane Electric LLCTransitIPv4 IPv621
AS12695LLC Digital NetworkHostingIPv620
AS24482SG.GSHostingIPv4 IPv68

All 15 upstreams →

Transit

Downstream networks

inferred

Networks for which AS201119 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 15

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4144
AS31500Global Network Management IncUnclassifiedIPv4 IPv694
AS50673Serverius Holding B.V.UnclassifiedIPv474
AS41095IPTP LTDHostingIPv460
AS20764CJSC RASCOMUnclassifiedIPv4 IPv652
AS1299Arelion Sweden ABTransitIPv438
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv630
AS6939Hurricane Electric LLCTransitIPv4 IPv621
AS12695LLC Digital NetworkHostingIPv620
AS24482SG.GSHostingIPv4 IPv68

All 15 adjacent →

Provenance

Where this comes from

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