asn.dev

Observed topology

AS210732 KAMANET Alexandre Fernandes

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210732: 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
AS209768white2net SrlResidentialIPv4 IPv6288
AS6939Hurricane Electric LLCTransitIPv4 IPv666
AS1103SURF B.V.UnclassifiedIPv43
AS5405Inter.link GmbHUnclassifiedIPv43
AS24482SG.GSHostingIPv43
AS31500Global Network Management IncUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200056INFRARINOXHostingIPv4 IPv6156
AS214326PERGAUD ErwanUnclassifiedIPv4 IPv693
AS211377ARYK SASUnclassifiedIPv633

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS209768white2net SrlResidentialIPv4 IPv6538
AS200056INFRARINOXHostingIPv4 IPv6156
AS214326PERGAUD ErwanUnclassifiedIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS211377ARYK SASUnclassifiedIPv633
AS1103SURF B.V.UnclassifiedIPv45
AS5405Inter.link GmbHUnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS31500Global Network Management IncUnclassifiedIPv45
AS34927iFog GmbHHostingIPv45

All 11 adjacent →

Provenance

Where this comes from

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