asn.dev

Observed topology

AS397326 SFN-ASN - South Front Networks

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS397326: 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
AS10242US Internet CorpResidentialIPv4 IPv669
AS32621Twin City VoIP, Inc.HostingIPv452
AS6939Hurricane Electric LLCTransitIPv634
AS24482SG.GSHostingIPv4 IPv63
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv63
AS3130RGnet OUUnclassifiedIPv42
AS9002RETN LimitedUnclassifiedIPv42
AS34927iFog GmbHHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63293Facebook, Inc.HostingIPv4 IPv6101

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS10242US Internet CorpResidentialIPv4 IPv6104
AS63293Facebook, Inc.HostingIPv4 IPv6101
AS32621Twin City VoIP, Inc.HostingIPv478
AS6939Hurricane Electric LLCTransitIPv667
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv43
AS9002RETN LimitedUnclassifiedIPv43
AS34927iFog GmbHHostingIPv43

Provenance

Where this comes from

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