asn.dev

Observed topology

AS43142 ADELINOVIUS

Residential RIPE Cable/DSL/ISP

Upstreams 15 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 10
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 15

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
AS174Cogent Communications, LLCTransitIPv4 IPv6258
AS2914NTT America, Inc.TransitIPv4 IPv6161
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS9002RETN LimitedUnclassifiedIPv613
AS5405Inter.link GmbHUnclassifiedIPv4 IPv69
AS20766Association "Gitoyen"UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS13030Init7 (Switzerland) Ltd.HostingIPv68
AS33891Core-Backbone GmbHHostingIPv42

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
AS6050201 SYSTEM SRLResidentialIPv459

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6391
AS50133Wimifi Systems Telecom and Electronics SARLUnclassifiedIPv4295
AS2914NTT America, Inc.TransitIPv4 IPv6282
AS6939Hurricane Electric LLCTransitIPv4 IPv6190
AS6050201 SYSTEM SRLResidentialIPv459
AS9002RETN LimitedUnclassifiedIPv615
AS5405Inter.link GmbHUnclassifiedIPv4 IPv614
AS20766Association "Gitoyen"UnclassifiedIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614

Provenance

Where this comes from

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