asn.dev

Observed topology

AS214159 CHERRYSERVERS5-AS UAB "Cherry Servers"

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214159: 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 IPv6531
AS9002RETN LimitedUnclassifiedIPv4520
AS2914NTT America, Inc.TransitIPv4357
AS33891Core-Backbone GmbHHostingIPv455
AS50304Blix Solutions ASUnclassifiedIPv452
AS12552GlobalConnect ABUnclassifiedIPv426
AS20764CJSC RASCOMUnclassifiedIPv426
AS24482SG.GSHostingIPv426
AS6206Netrouting B.V.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197622NEXTTRANSLATE LTDUnclassifiedIPv460
AS198420Netly LLCUnclassifiedIPv460
AS198661Ksenia BeckerUnclassifiedIPv460
AS203614NEXTTRANSLATE LTDUnclassifiedIPv460
AS219335COREVANCE LTDUnclassifiedIPv460
AS198180Gabriele SabatinoUnclassifiedIPv459

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4668
AS1299Arelion Sweden ABTransitIPv4 IPv6663
AS2914NTT America, Inc.TransitIPv4436
AS197622NEXTTRANSLATE LTDUnclassifiedIPv460
AS198420Netly LLCUnclassifiedIPv460
AS198661Ksenia BeckerUnclassifiedIPv460
AS203614NEXTTRANSLATE LTDUnclassifiedIPv460
AS219335COREVANCE LTDUnclassifiedIPv460
AS198180Gabriele SabatinoUnclassifiedIPv459
AS33891Core-Backbone GmbHHostingIPv455

All 15 adjacent →

Provenance

Where this comes from

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