asn.dev

Observed topology

AS219521 VERSADC - VERSADC VERI MERKEZI HIZMETLERI LIMITED SIRKETI

Unclassified RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS219521: 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
AS42216Netviser Bilisim Teknolojileri San. Ve Tic. Ltd. Sti.HostingIPv4174
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv43
AS206119Veganet Teknolojileri ve Hizmetleri LTD STIUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34987eva bilgi teknolojileri san ve tic ltd stiUnclassifiedIPv4180
AS211539YUSUF OZTURKUnclassifiedIPv4119

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS42216Netviser Bilisim Teknolojileri San. Ve Tic. Ltd. Sti.HostingIPv4467
AS34987eva bilgi teknolojileri san ve tic ltd stiUnclassifiedIPv4180
AS211539YUSUF OZTURKUnclassifiedIPv4119
AS206119Veganet Teknolojileri ve Hizmetleri LTD STIUnclassifiedIPv49
AS9121Turk Telekomunikasyon Anonim SirketiMobileIPv43

Provenance

Where this comes from

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