asn.dev

Observed topology

AS17223 DATABANK-LATISYS

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17223: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6926
AS6461Zayo BandwidthTransitIPv4 IPv6909

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS63201Coeo Solutions, LLCUnclassifiedIPv4960
AS36475Zacks Investment Research Inc.UnclassifiedIPv4120
AS23008NORCUnclassifiedIPv4 IPv693
AS21914RXO Corporate Solutions, LLCUnclassifiedIPv460
AS54963Lume Technologies Inc.UnclassifiedIPv460
AS63291Addus Healthcare, IncUnclassifiedIPv460
AS395773Collegis EducationUnclassifiedIPv460
AS398746HARRIS & HARRIS, LTD.UnclassifiedIPv460
AS23438EZLinks Golf, Inc.UnclassifiedIPv458
AS16563Nexum, Inc.UnclassifiedIPv439

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,771
AS6461Zayo BandwidthTransitIPv4 IPv61,681
AS63201Coeo Solutions, LLCUnclassifiedIPv4986
AS36475Zacks Investment Research Inc.UnclassifiedIPv4120
AS23008NORCUnclassifiedIPv4 IPv693
AS21914RXO Corporate Solutions, LLCUnclassifiedIPv460
AS54963Lume Technologies Inc.UnclassifiedIPv460
AS63291Addus Healthcare, IncUnclassifiedIPv460
AS395773Collegis EducationUnclassifiedIPv460
AS398746HARRIS & HARRIS, LTD.UnclassifiedIPv460

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.