asn.dev

Observed topology

AS3238 ALCOM

Residential RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS3238: 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
AS42649Baffin Bay Networks ABUnclassifiedIPv4 IPv6984
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv6166
AS33891Core-Backbone GmbHHostingIPv426
AS8434Telenor Sverige ABResidentialIPv424
AS12552GlobalConnect ABUnclassifiedIPv424
AS50304Blix Solutions ASUnclassifiedIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv616
AS3216PJSC "Vimpelcom"MobileIPv415
AS3303Swisscom (Schweiz) AGResidentialIPv415

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41878Crosskey Banking Solutions Ab LtdUnclassifiedIPv416

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS42649Baffin Bay Networks ABUnclassifiedIPv4 IPv6994
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv6166
AS12552GlobalConnect ABUnclassifiedIPv426
AS33891Core-Backbone GmbHHostingIPv426
AS8434Telenor Sverige ABResidentialIPv424
AS50304Blix Solutions ASUnclassifiedIPv4 IPv619
AS3303Swisscom (Schweiz) AGResidentialIPv417
AS24482SG.GSHostingIPv4 IPv616
AS41878Crosskey Banking Solutions Ab LtdUnclassifiedIPv416

All 15 adjacent →

Provenance

Where this comes from

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