asn.dev

Observed topology

AS10913 INTERNAP-BLK

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10913: 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
AS1828Unitas GlobalUnclassifiedIPv4 IPv62,040

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS393954CFN Services Inc.UnclassifiedIPv4 IPv6363
AS19133Bird Hosting Inc.HostingIPv4 IPv6306
AS40620QIAGEN Redwood City, Inc.UnclassifiedIPv4171
AS13443LinkedIn CorporationUnclassifiedIPv4 IPv6144
AS399740NEOGOVUnclassifiedIPv4118
AS54876ROKABEAR LLCUnclassifiedIPv4114
AS18608PALADYNE SYSTEMS, LLCUnclassifiedIPv4110
AS54993OpsRamp, LLCUnclassifiedIPv4110
AS20249Jefferies LLCUnclassifiedIPv4105
AS40889Greystone IT, Inc.UnclassifiedIPv464

All 13 downstreams →

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS1828Unitas GlobalUnclassifiedIPv4 IPv63,822
AS393954CFN Services Inc.UnclassifiedIPv4 IPv6363
AS19133Bird Hosting Inc.HostingIPv4 IPv6306
AS40620QIAGEN Redwood City, Inc.UnclassifiedIPv4171
AS13443LinkedIn CorporationUnclassifiedIPv4 IPv6144
AS399740NEOGOVUnclassifiedIPv4118
AS54876ROKABEAR LLCUnclassifiedIPv4114
AS18608PALADYNE SYSTEMS, LLCUnclassifiedIPv4110
AS54993OpsRamp, LLCUnclassifiedIPv4110
AS20249Jefferies LLCUnclassifiedIPv4105

All 14 adjacent →

Provenance

Where this comes from

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