Observed topology
AS59692 IQWEB IQWeb FZ-LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS59692: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 838 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 443 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 255 |
| AS57724 | DDOS-GUARD LTD | Unclassified | IPv4 | 60 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 36 |
| AS24482 | SG.GS | Hosting | IPv4 | 36 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 34 |
| AS4657 | StarHub Ltd | Residential | IPv4 | 34 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 34 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 34 |
Transit
Downstream networks
Networks for which AS59692 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57724 | DDOS-GUARD LTD | Unclassified | IPv4 IPv6 | 1,711 |
| AS9123 | JSC "TIMEWEB" | Hosting | IPv4 | 1,401 |
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 | 868 |
| AS200436 | Patron Technology Persia Ltd | Unclassified | IPv4 | 672 |
| AS50867 | HOSTKEY B.V. | Hosting | IPv4 | 597 |
| AS51698 | "ActiveHost RU" LLC | Unclassified | IPv4 | 508 |
| AS50340 | JSC Selectel | Hosting | IPv4 | 497 |
| AS29182 | JSC IOT | Hosting | IPv4 | 448 |
| AS211642 | AdminVPS OOO | Unclassified | IPv4 | 389 |
| AS49505 | JSC Selectel | Hosting | IPv4 | 335 |
Adjacency
Adjacent networks
Every AS seen directly next to AS59692 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 8,951 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 5,055 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 4,504 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 2,594 |
| AS57724 | DDOS-GUARD LTD | Unclassified | IPv4 IPv6 | 1,771 |
| AS39561 | "Domain names registrar REG.RU", Ltd | Unclassified | IPv4 IPv6 | 1,518 |
| AS9123 | JSC "TIMEWEB" | Hosting | IPv4 | 1,401 |
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 | 892 |
| AS200436 | Patron Technology Persia Ltd | Unclassified | IPv4 | 672 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 653 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.