asn.dev

Observed topology

AS19024 INTERNAP-BLK5

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19024: 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 IPv61,391

Transit

Downstream networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS14148Ex Libris (USA) IncUnclassifiedIPv4 IPv6448
AS22481Encore Group (USA) LLCUnclassifiedIPv4224
AS15220-Reserved AS-UnclassifiedIPv4177
AS19812BT Americas, IncUnclassifiedIPv4118
AS21734Trading Technologies Intl, Inc.UnclassifiedIPv4112
AS63018Dedicated.comHostingIPv4109
AS22075Outbrain, Inc.UnclassifiedIPv488
AS18830HMHUnclassifiedIPv459
AS22276BankUnited NAUnclassifiedIPv459
AS32957FactSet Research Systems, Inc.UnclassifiedIPv459

All 24 downstreams →

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS1828Unitas GlobalUnclassifiedIPv4 IPv63,460
AS14148Ex Libris (USA) IncUnclassifiedIPv4 IPv6448
AS22481Encore Group (USA) LLCUnclassifiedIPv4224
AS15220-Reserved AS-UnclassifiedIPv4177
AS63018Dedicated.comHostingIPv4 IPv6133
AS19812BT Americas, IncUnclassifiedIPv4118
AS21734Trading Technologies Intl, Inc.UnclassifiedIPv4112
AS22075Outbrain, Inc.UnclassifiedIPv488
AS393954CFN Services Inc.UnclassifiedIPv471
AS18830HMHUnclassifiedIPv459

All 25 adjacent →

Provenance

Where this comes from

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