asn.dev

Observed topology

AS399728 PFOUNDATION

Unclassified ARIN

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS399728: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6578
AS174Cogent Communications, LLCTransitIPv4 IPv697
AS24482SG.GSHostingIPv4 IPv616
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv616
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS48185team.blue NVUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv66
AS50304Blix Solutions ASUnclassifiedIPv45

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54994Meteverse Limited.UnclassifiedIPv460

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6584
AS174Cogent Communications, LLCTransitIPv4 IPv6134
AS54994Meteverse Limited.UnclassifiedIPv460
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv617
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv67

All 20 adjacent →

Provenance

Where this comes from

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