asn.dev

Observed topology

AS44141 DEVCLIC-AS DEVCLIC SARL

Hosting RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS44141: 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
AS2914NTT America, Inc.TransitIPv486
AS174Cogent Communications, LLCTransitIPv478
AS6939Hurricane Electric LLCTransitIPv432
AS1103SURF B.V.UnclassifiedIPv44
AS6696VERIXI SAUnclassifiedIPv44
AS12779IT.Gate S.p.A.UnclassifiedIPv44
AS24482SG.GSHostingIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS34019Hivane AssociationUnclassifiedIPv44
AS34927iFog GmbHHostingIPv44

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59911P.C. & Associes SRLUnclassifiedIPv458
AS196658TRUST INFO s.a.r.l.UnclassifiedIPv451
AS197551Ameos SARLHostingIPv428

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4182
AS174Cogent Communications, LLCTransitIPv480
AS196658TRUST INFO s.a.r.l.UnclassifiedIPv469
AS6939Hurricane Electric LLCTransitIPv459
AS59911P.C. & Associes SRLUnclassifiedIPv458
AS197551Ameos SARLHostingIPv428
AS6696VERIXI SAUnclassifiedIPv411
AS24482SG.GSHostingIPv49
AS12779IT.Gate S.p.A.UnclassifiedIPv47
AS33891Core-Backbone GmbHHostingIPv47

All 16 adjacent →

Provenance

Where this comes from

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