Observed topology
AS39326 HSO-GROUP Syntura Group Limited
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS39326: 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 IPv6 | 740 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 422 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 287 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 60 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 35 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 35 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 35 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 35 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 31 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 30 |
Transit
Downstream networks
Networks for which AS39326 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41489 | Watchfront Limited | Hosting | IPv4 | 240 |
| AS199448 | Babble Cloud Holdings Ltd. | Unclassified | IPv4 | 236 |
| AS202020 | Flexgrid Ltd | Residential | IPv4 | 135 |
| AS209113 | Precedence Technologies Ltd | Unclassified | IPv4 | 118 |
| AS5500 | Chess ICT Ltd | Residential | IPv4 IPv6 | 106 |
| AS200652 | Nuvias UC Limited | Unclassified | IPv4 IPv6 | 90 |
| AS201226 | Leasing Options Limited | Unclassified | IPv4 | 78 |
| AS15689 | Advanced IT Services Nottingham Ltd | Unclassified | IPv4 IPv6 | 72 |
| AS59565 | Cronos Internet Ltd | Unclassified | IPv4 IPv6 | 62 |
| AS50888 | Minotaur I.T. Limited | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39326 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,183 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 912 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 453 |
| AS39545 | Fluidone Ltd. | Unclassified | IPv4 IPv6 | 262 |
| AS41489 | Watchfront Limited | Hosting | IPv4 | 240 |
| AS199448 | Babble Cloud Holdings Ltd. | Unclassified | IPv4 | 236 |
| AS202020 | Flexgrid Ltd | Residential | IPv4 | 153 |
| AS209113 | Precedence Technologies Ltd | Unclassified | IPv4 | 118 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 116 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 110 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-06 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.