asn.dev

Observed topology

AS39421 SAPINET-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39421: 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
AS47160MOJI SASResidentialIPv4 IPv6225
AS3257GTT Communications Inc.TransitIPv4 IPv6107
AS6939Hurricane Electric LLCTransitIPv4 IPv653
AS204092Association GRIFONUnclassifiedIPv4 IPv66
AS6696VERIXI SAUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211352Tom MARQUAILLE trading as OBSIDIAN COREUnclassifiedIPv4 IPv692
AS62430Alce LafranqueUnclassifiedIPv635

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS47160MOJI SASResidentialIPv4 IPv6242
AS3257GTT Communications Inc.TransitIPv4 IPv6176
AS211352Tom MARQUAILLE trading as OBSIDIAN COREUnclassifiedIPv4 IPv692
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS62430Alce LafranqueUnclassifiedIPv635
AS204092Association GRIFONUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv46
AS25091IP-Max SAUnclassifiedIPv61
AS34927iFog GmbHHostingIPv41

Provenance

Where this comes from

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