Observed topology
AS202365 CHRONOS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS202365: 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 |
|---|---|---|---|---|
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 153 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 145 |
| AS62240 | Clouvider Limited | Hosting | IPv4 IPv6 | 78 |
| AS208594 | Netbone Telekomunikasyon A.S. | Unclassified | IPv4 | 59 |
| AS34872 | Sarah Rossius trading as Servperso Systems | Hosting | IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 1 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 1 |
| AS57821 | Nonattached Network e.V. | Unclassified | IPv4 | 1 |
| AS57866 | Fusix Networks B.V. | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS202365 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 3,280 |
| AS51559 | Netinternet Bilisim Teknolojileri AS | Hosting | IPv6 | 2,671 |
| AS15169 | Google LLC | Hosting | IPv4 | 980 |
| AS16276 | OVH SAS | Hosting | IPv4 | 674 |
| AS12586 | GHOSTnet GmbH | Hosting | IPv4 | 463 |
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 | 270 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 236 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 | 113 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 107 |
| AS57344 | Telehouse EAD | Residential | IPv4 | 104 |
Adjacency
Adjacent networks
Every AS seen directly next to AS202365 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 1,019,749 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 167,928 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 16,234 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 6,969 |
| AS24482 | SG.GS | Hosting | IPv4 | 6,621 |
| AS22356 | Durand do Brasil Ltda | Unclassified | IPv4 | 5,650 |
| AS15169 | Google LLC | Hosting | IPv4 | 4,780 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 3,622 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 3,218 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 3,167 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.