asn.dev

Observed topology

AS396998 PATH-NETWORK

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396998: 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
AS3257GTT Communications Inc.TransitIPv4 IPv61,438
AS9002RETN LimitedUnclassifiedIPv4 IPv6400

Transit

Downstream networks

All 48

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

ASNetworkTypeFamiliesPaths seen
AS8796FASTNET DATA INCHostingIPv4939
AS36231FZCOHostingIPv4 IPv6905
AS46475Limestone Networks, Inc.HostingIPv4788
AS18779EGIHostingHostingIPv4730
AS216030GoodLeaf Hosting & Development LLCHostingIPv4 IPv6681
AS8893Artfiles New Media GmbHHostingIPv4 IPv6572
AS399250Name Hero, LLCUnclassifiedIPv4413
AS20278Nexeon Technologies, Inc.HostingIPv4353
AS22184IRIDIUM SATELLITE,LLCUnclassifiedIPv4353
AS26904Nasulex NetworksUnclassifiedIPv4 IPv6313

All 48 downstreams →

Adjacency

Adjacent networks

All 51

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv610,361
AS9002RETN LimitedUnclassifiedIPv4 IPv61,688
AS8796FASTNET DATA INCHostingIPv4997
AS36231FZCOHostingIPv4 IPv6905
AS46475Limestone Networks, Inc.HostingIPv4885
AS18779EGIHostingHostingIPv4787
AS216030GoodLeaf Hosting & Development LLCHostingIPv4 IPv6681
AS8893Artfiles New Media GmbHHostingIPv4 IPv6572
AS20278Nexeon Technologies, Inc.HostingIPv4415
AS399250Name Hero, LLCUnclassifiedIPv4413

All 51 adjacent →

Provenance

Where this comes from

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