asn.dev

Observed topology

AS59642 CHERRYSERVERS2-AS

Hosting RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS59642: 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
AS60068Datacamp LimitedHostingIPv4 IPv6412
AS9002RETN LimitedUnclassifiedIPv4 IPv6403
AS1299Arelion Sweden ABTransitIPv4 IPv6248
AS2914NTT America, Inc.TransitIPv4225
AS50304Blix Solutions ASUnclassifiedIPv444
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv422
AS6696VERIXI SAUnclassifiedIPv422
AS17639Converge ICT Solutions Inc.UnclassifiedIPv422
AS20485Joint Stock Company TransTeleComUnclassifiedIPv422
AS24482SG.GSHostingIPv422

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198661Ksenia BeckerUnclassifiedIPv463

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6435
AS9002RETN LimitedUnclassifiedIPv4 IPv6423
AS1299Arelion Sweden ABTransitIPv4 IPv6258
AS2914NTT America, Inc.TransitIPv4235
AS198661Ksenia BeckerUnclassifiedIPv463
AS50304Blix Solutions ASUnclassifiedIPv444
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv422
AS6696VERIXI SAUnclassifiedIPv422
AS17639Converge ICT Solutions Inc.UnclassifiedIPv422
AS20485Joint Stock Company TransTeleComUnclassifiedIPv422

Provenance

Where this comes from

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