asn.dev

Observed topology

AS43142 AdeliNovius ADELI SAS

Residential RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS43142: 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.TransitIPv4 IPv6604
AS174Cogent Communications, LLCTransitIPv4 IPv6216
AS6939Hurricane Electric LLCTransitIPv4 IPv6152
AS6461Zayo BandwidthTransitIPv4 IPv644
AS34019Hivane AssociationUnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv69
AS13030Init7 (Switzerland) Ltd.HostingIPv68
AS6696VERIXI SAUnclassifiedIPv41
AS12779IT.Gate S.p.A.UnclassifiedIPv41
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50133Wimifi Systems Telecom and Electronics SARLUnclassifiedIPv4295
AS50818Muona SASUnclassifiedIPv488
AS6050201 SYSTEM SRLResidentialIPv456
AS61026HASGARD s.a.r.l.UnclassifiedIPv434

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6797
AS174Cogent Communications, LLCTransitIPv4 IPv6332
AS50133Wimifi Systems Telecom and Electronics SARLUnclassifiedIPv4295
AS6939Hurricane Electric LLCTransitIPv4 IPv6250
AS50818Muona SASUnclassifiedIPv4110
AS61026HASGARD s.a.r.l.UnclassifiedIPv457
AS6050201 SYSTEM SRLResidentialIPv456
AS6461Zayo BandwidthTransitIPv4 IPv650
AS24482SG.GSHostingIPv4 IPv632
AS34019Hivane AssociationUnclassifiedIPv4 IPv629

Provenance

Where this comes from

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