Observed topology
AS35614 therecomltd Therecom Ltd
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS35614: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 395 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 139 |
| AS3326 | PRIVATE JOINT STOCK COMPANY "DATAGROUP" | Residential | IPv4 IPv6 | 101 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 53 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 52 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 22 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 12 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv6 | 7 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS35614 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56465 | Therecom Ltd | Unclassified | IPv4 IPv6 | 926 |
| AS25505 | LUX GROUP, LLC | Unclassified | IPv4 | 199 |
| AS21312 | LUX GROUP, LLC | Unclassified | IPv4 | 198 |
| AS60918 | Kharkiv National Automobile and Highway University | Unclassified | IPv4 IPv6 | 102 |
| AS29035 | DaNet Ltd. | Unclassified | IPv4 IPv6 | 96 |
| AS215950 | Municipal Enterprise of Kharkiv Regional Council "Kharkiv Oblast Communication Systems" | Unclassified | IPv4 | 66 |
| AS51738 | FOP Masaltsev Denis Leonidovich | Unclassified | IPv4 | 64 |
| AS58199 | FLP Lialiuk Andrey Nikolaevich | Unclassified | IPv4 | 64 |
| AS198958 | LLC "APTEKA911.UA" | Unclassified | IPv4 | 59 |
| AS21029 | Kharkiv Regional State Administration | Unclassified | IPv4 | 50 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35614 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,624 |
| AS56465 | Therecom Ltd | Unclassified | IPv4 IPv6 | 926 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 369 |
| AS3326 | PRIVATE JOINT STOCK COMPANY "DATAGROUP" | Residential | IPv4 IPv6 | 329 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 219 |
| AS25505 | LUX GROUP, LLC | Unclassified | IPv4 | 199 |
| AS21312 | LUX GROUP, LLC | Unclassified | IPv4 | 198 |
| AS44383 | KP "CIC" Kharkov | Unclassified | IPv4 | 195 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 143 |
| AS60918 | Kharkiv National Automobile and Highway University | Unclassified | IPv4 IPv6 | 102 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.36M 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.