asn.dev

Observed topology

AS62443 AKWA Nicolas VUILLERMET

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62443: 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 IPv6103
AS6939Hurricane Electric LLCTransitIPv4 IPv645
AS60132Zoreole Group SARLHostingIPv4 IPv617
AS204092Association GRIFONUnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205305Gabriel PeronUnclassifiedIPv4 IPv6160
AS215528InfoGenius SASUnclassifiedIPv4 IPv6135
AS218582VOLUNIAUnclassifiedIPv4 IPv664
AS207849ESIEESPACEUnclassifiedIPv4 IPv641
AS215529Arnaud TARDYUnclassifiedIPv636
AS208705NIIT SASUUnclassifiedIPv4 IPv626

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv6404
AS215528InfoGenius SASUnclassifiedIPv4 IPv6170
AS205305Gabriel PeronUnclassifiedIPv4 IPv6160
AS6939Hurricane Electric LLCTransitIPv4 IPv6156
AS60132Zoreole Group SARLHostingIPv4 IPv6111
AS207849ESIEESPACEUnclassifiedIPv4 IPv668
AS218582VOLUNIAUnclassifiedIPv4 IPv664
AS215529Arnaud TARDYUnclassifiedIPv636
AS208705NIIT SASUUnclassifiedIPv4 IPv626
AS204092Association GRIFONUnclassifiedIPv4 IPv616

All 11 adjacent →

Provenance

Where this comes from

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