asn.dev

Observed topology

AS398991 X99-US - X99

Hosting ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS398991: 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
AS2914NTT America, Inc.TransitIPv4 IPv6808
AS60068Datacamp LimitedHostingIPv4 IPv6787
AS272786X99 INTERNETHostingIPv4 IPv6610
AS6939Hurricane Electric LLCTransitIPv4 IPv6513
AS174Cogent Communications, LLCTransitIPv4 IPv6354
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6205
AS24482SG.GSHostingIPv4 IPv622
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv621
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv611
AS971PureVoltage Hosting Inc.UnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS272786X99 INTERNETHostingIPv491
AS274365IT TECNOLOGIA EM TI LTDAUnclassifiedIPv458
AS402008L7CORE, LLCUnclassifiedIPv631

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6881
AS60068Datacamp LimitedHostingIPv4 IPv6804
AS272786X99 INTERNETHostingIPv4 IPv6701
AS6939Hurricane Electric LLCTransitIPv4 IPv6535
AS174Cogent Communications, LLCTransitIPv4 IPv6394
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6229
AS274365IT TECNOLOGIA EM TI LTDAUnclassifiedIPv458
AS402008L7CORE, LLCUnclassifiedIPv631
AS24482SG.GSHostingIPv4 IPv623
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv622

Provenance

Where this comes from

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