asn.dev

Observed topology

AS19531 NODESDIRECT - Nodes Direct

Hosting ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19531: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6311
AS174Cogent Communications, LLCTransitIPv4 IPv6176
AS6939Hurricane Electric LLCTransitIPv4 IPv6129
AS3257GTT Communications Inc.TransitIPv4 IPv6118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS22653Cyber Wurx LLCHostingIPv4 IPv6248
AS11230Managed Hosting Services, LLCHostingIPv4117
AS43737Nodes Direct Holdings LLCUnclassifiedIPv458
AS21635World Wide Communications USA Inc.UnclassifiedIPv424
AS32488CompassMSP, LLC.UnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22653Cyber Wurx LLCHostingIPv4 IPv65,980
AS1299Arelion Sweden ABTransitIPv4 IPv64,191
AS174Cogent Communications, LLCTransitIPv4 IPv61,272
AS6939Hurricane Electric LLCTransitIPv4 IPv6764
AS3257GTT Communications Inc.TransitIPv4 IPv6698
AS11230Managed Hosting Services, LLCHostingIPv4117
AS43737Nodes Direct Holdings LLCUnclassifiedIPv458
AS21635World Wide Communications USA Inc.UnclassifiedIPv424
AS32488CompassMSP, LLC.UnclassifiedIPv412

Provenance

Where this comes from

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