Observed topology
AS35598 INETCOM
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS35598: 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 |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 489 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 265 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 151 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 149 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 139 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 136 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 52 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 52 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 44 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 31 |
Transit
Downstream networks
Networks for which AS35598 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39238 | OKB PROGRESS LLC | Hosting | IPv4 IPv6 | 7,582 |
| AS15672 | OOO Telecom TZ | Unclassified | IPv4 IPv6 | 2,627 |
| AS49531 | "NetCom-R" LLC | Unclassified | IPv4 IPv6 | 2,470 |
| AS59504 | LLC Vpsville | Unclassified | IPv4 | 1,999 |
| AS204490 | Kontel LLC | Unclassified | IPv4 IPv6 | 1,732 |
| AS41039 | Timer, LLC | Unclassified | IPv4 | 1,489 |
| AS60246 | Consumer Internet Cooperative PG-19 | Unclassified | IPv4 IPv6 | 1,307 |
| AS25308 | CityLanCom LTD | Unclassified | IPv4 | 1,228 |
| AS204720 | GLOBAL CLOUD NETWORK LLC | Hosting | IPv4 IPv6 | 1,145 |
| AS207713 | GLOBAL INTERNET SOLUTIONS LLC | Hosting | IPv4 IPv6 | 1,000 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35598 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 68,987 |
| AS12722 | RECONN LLC | Hosting | IPv4 IPv6 | 9,453 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 9,433 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 8,577 |
| AS39238 | OKB PROGRESS LLC | Hosting | IPv4 IPv6 | 8,422 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 7,924 |
| AS35196 | FIRST SERVER LIMITED | Hosting | IPv4 IPv6 | 6,748 |
| AS47775 | JSC "Ufanet" | Unclassified | IPv4 | 5,660 |
| AS50113 | FIRST SERVER LIMITED | Unclassified | IPv4 IPv6 | 4,371 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 3,878 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.