asn.dev

Observed topology

AS43858 ASN-WEBAXYS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS43858: 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
AS62000SERVERD SASHostingIPv4 IPv6234
AS6939Hurricane Electric LLCTransitIPv4 IPv6105
AS3356Level 3 Parent, LLCTransitIPv4 IPv672
AS174Cogent Communications, LLCTransitIPv4 IPv661
AS201675SACLAK NETWORK SASResidentialIPv421
AS24482SG.GSHostingIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS204092Association GRIFONUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213047GAMAC S.A.R.L.UnclassifiedIPv422

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv6234
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS3356Level 3 Parent, LLCTransitIPv4 IPv680
AS174Cogent Communications, LLCTransitIPv4 IPv661
AS213047GAMAC S.A.R.L.UnclassifiedIPv422
AS201675SACLAK NETWORK SASResidentialIPv421
AS24482SG.GSHostingIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS204092Association GRIFONUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv47

All 12 adjacent →

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.