asn.dev

Observed topology

AS62217 VooServers Vinters IT Ltd

Unclassified RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS62217: 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 IPv6358
AS11403NYIHostingIPv4 IPv6230
AS3257GTT Communications Inc.TransitIPv4 IPv6205
AS6461Zayo BandwidthTransitIPv4 IPv6204
AS3223Voxility LLPHostingIPv4168
AS174Cogent Communications, LLCTransitIPv4133
AS34549meerfarbig GmbH & Co. KGHostingIPv445
AS4744723M GmbHHostingIPv4 IPv644
AS50304Blix Solutions ASUnclassifiedIPv430
AS3741Dimension DataUnclassifiedIPv415

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9515Compute Global LimitedUnclassifiedIPv4 IPv6150
AS39459Office Unlocked LimitedUnclassifiedIPv458

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS9515Compute Global LimitedUnclassifiedIPv4 IPv6750
AS6461Zayo BandwidthTransitIPv4 IPv6694
AS3257GTT Communications Inc.TransitIPv4 IPv6407
AS6939Hurricane Electric LLCTransitIPv4 IPv6358
AS11403NYIHostingIPv4 IPv6230
AS3223Voxility LLPHostingIPv4208
AS174Cogent Communications, LLCTransitIPv4196
AS39459Office Unlocked LimitedUnclassifiedIPv458
AS34549meerfarbig GmbH & Co. KGHostingIPv445
AS4744723M GmbHHostingIPv4 IPv644

All 24 adjacent →

Provenance

Where this comes from

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