Observed topology
AS216265 ARISTO-NET ARISTO NETWORKS LTD
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS216265: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 13 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 12 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 11 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 6 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 5 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 4 |
| AS1273 | IDDQD-AS | Business | IPv4 | 3 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 2 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 2 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 2 |
Transit
Downstream networks
Networks for which AS216265 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60064 | HOSTPALACE DATACENTERS LTD | Unclassified | IPv4 IPv6 | 2,244 |
| AS50049 | RedSwitches | Hosting | IPv4 IPv6 | 1,313 |
| AS206389 | Menno van Krimpen trading as Libernet | Residential | IPv4 | 310 |
| AS204729 | Xaviero Xaviel Kajafas trading as Internalhost | Hosting | IPv4 | 176 |
| AS51265 | Mass Response Service GmbH | Residential | IPv4 | 149 |
| AS211316 | Adyen N.V. | Unclassified | IPv4 | 98 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 40 |
Adjacency
Adjacent networks
Every AS seen directly next to AS216265 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60064 | HOSTPALACE DATACENTERS LTD | Unclassified | IPv4 IPv6 | 3,953 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 IPv6 | 3,291 |
| AS50049 | RedSwitches | Hosting | IPv4 IPv6 | 2,020 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,363 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 983 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 896 |
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 630 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 507 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 456 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 444 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.