asn.dev

Observed topology

AS39855 MOD-EU

Hosting RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS39855: 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
AS1299Arelion Sweden ABTransitIPv4 IPv67,495
AS3257GTT Communications Inc.TransitIPv4 IPv66,669
AS5511Orange S.A.TransitIPv42,686
AS3491PCCW Global (HK) Ltd.TransitIPv42,140
AS12741Netia SAResidentialIPv41,692
AS174Cogent Communications, LLCTransitIPv41,363
AS31122Digiweb ltdUnclassifiedIPv41,135
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv41,109
AS6939Hurricane Electric LLCTransitIPv4 IPv61,030
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.UnclassifiedIPv4910

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48806Stackster LLCUnclassifiedIPv42,415

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv69,458
AS3257GTT Communications Inc.TransitIPv4 IPv66,797
AS5511Orange S.A.TransitIPv43,010
AS48806Stackster LLCUnclassifiedIPv42,415
AS3491PCCW Global (HK) Ltd.TransitIPv42,140
AS12741Netia SAResidentialIPv41,692
AS174Cogent Communications, LLCTransitIPv41,363
AS31122Digiweb ltdUnclassifiedIPv41,135
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv41,109
AS6939Hurricane Electric LLCTransitIPv4 IPv61,030

All 25 adjacent →

Provenance

Where this comes from

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