Observed topology
AS202365 Chronos Omer GOLGELI
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 | 144 |
| AS62240 | Clouvider Limited | Hosting | IPv4 IPv6 | 80 |
| AS208594 | Netbone Telekomunikasyon A.S. | Unclassified | IPv4 | 60 |
| 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 |
| AS401753 | BIXCE Inc | 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,367 |
| AS15169 | Google LLC | Hosting | IPv4 | 987 |
| AS51559 | Netinternet Bilisim Teknolojileri AS | Hosting | IPv6 | 691 |
| AS16276 | OVH SAS | Hosting | IPv4 | 630 |
| AS12586 | GHOSTnet GmbH | Hosting | IPv4 | 445 |
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 | 298 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 238 |
| AS49453 | Global Layer B.V. | Hosting | IPv4 | 137 |
| AS49981 | WorldStream B.V. | Hosting | IPv4 | 116 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 105 |
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,027,210 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 163,494 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 16,267 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 10,671 |
| AS24482 | SG.GS | Hosting | IPv4 | 6,654 |
| AS15169 | Google LLC | Hosting | IPv4 | 4,785 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 3,478 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 3,339 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 3,338 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 2,571 |
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.