asn.dev

Observed topology

AS42929 ARTEFACT Artewan, Operateur de reseaux et de services

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42929: 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
AS4455IX Reach LtdUnclassifiedIPv4 IPv6146
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6126
AS31216BSO Network Solutions SASUnclassifiedIPv4 IPv649
AS6939Hurricane Electric LLCTransitIPv448
AS24482SG.GSHostingIPv4 IPv67
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv67
AS37100SEACOM LimitedUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44606Artefact SARLUnclassifiedIPv4200

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS4455IX Reach LtdUnclassifiedIPv4 IPv6226
AS44606Artefact SARLUnclassifiedIPv4200
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6186
AS6939Hurricane Electric LLCTransitIPv478
AS31216BSO Network Solutions SASUnclassifiedIPv4 IPv667
AS24482SG.GSHostingIPv4 IPv611
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS37100SEACOM LimitedUnclassifiedIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS43531BSO Network Solutions SASUnclassifiedIPv42

All 11 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.