asn.dev

Observed topology

AS396998 PATH-NETWORK - Path Network, Inc.

Unclassified ARIN

Upstreams 2 carry this network
Downstreams 50 this network carries
Adjacent (IPv4) 53
Adjacent (IPv6) 9
Upstream graph Who carries AS396998, and who carries them, drawn as a map up to the transit-free core. 20 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,636
AS174Cogent Communications, LLCTransitIPv662

Transit

Downstream networks

All 50

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

ASNetworkTypeFamiliesPaths seen
AS8796FASTNET DATA INCHostingIPv41,026
AS46475Limestone Networks, Inc.HostingIPv4900
AS18779EGIHostingHostingIPv4731
AS36231FZCOHostingIPv4 IPv6696
AS216030GoodLeaf Hosting & Development LLCHostingIPv4 IPv6632
AS8893Artfiles New Media GmbHHostingIPv4 IPv6571
AS399250Name Hero, LLCUnclassifiedIPv4420
AS22184IRIDIUM SATELLITE,LLCUnclassifiedIPv4364
AS20278Nexeon Technologies, Inc.HostingIPv4360
AS26904Nasulex NetworksUnclassifiedIPv4 IPv6308

All 50 downstreams →

Adjacency

Adjacent networks

All 53

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv611,027
AS8796FASTNET DATA INCHostingIPv41,029
AS46475Limestone Networks, Inc.HostingIPv4980
AS18779EGIHostingHostingIPv4788
AS36231FZCOHostingIPv4 IPv6696
AS216030GoodLeaf Hosting & Development LLCHostingIPv4 IPv6632
AS174Cogent Communications, LLCTransitIPv4 IPv6622
AS8893Artfiles New Media GmbHHostingIPv4 IPv6571
AS20278Nexeon Technologies, Inc.HostingIPv4422
AS399250Name Hero, LLCUnclassifiedIPv4420

All 53 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.