asn.dev

Observed topology

AS19969 JOESDATACENTER

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19969: 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 IPv6565
AS6461Zayo BandwidthTransitIPv4 IPv6424
AS174Cogent Communications, LLCTransitIPv4 IPv6293
AS34927iFog GmbHHostingIPv4 IPv618
AS3257GTT Communications Inc.TransitIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13654KC Web, Inc.UnclassifiedIPv41,086
AS396004TIGER COMPUTER CONSULTING, LLCUnclassifiedIPv4564
AS25731Knox Box NetworksUnclassifiedIPv4 IPv6293
AS395129United Electric CooperativeUnclassifiedIPv4180
AS400659Davey Group LLCUnclassifiedIPv4 IPv6116
AS26457nonexiste.netUnclassifiedIPv4 IPv682
AS19556Isotech, IncUnclassifiedIPv459

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,586
AS6939Hurricane Electric LLCTransitIPv4 IPv61,526
AS13654KC Web, Inc.UnclassifiedIPv41,150
AS174Cogent Communications, LLCTransitIPv4 IPv6898
AS396004TIGER COMPUTER CONSULTING, LLCUnclassifiedIPv4564
AS395129United Electric CooperativeUnclassifiedIPv4495
AS25731Knox Box NetworksUnclassifiedIPv4 IPv6293
AS400659Davey Group LLCUnclassifiedIPv4 IPv6116
AS26457nonexiste.netUnclassifiedIPv4 IPv682
AS19556Isotech, IncUnclassifiedIPv459

All 12 adjacent →

Provenance

Where this comes from

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