Observed topology
AS39572 ADVANCEDHOSTERS-AS
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS39572: 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 | 2,545 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,111 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 774 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 719 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 658 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 65 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 63 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 57 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 IPv6 | 56 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 50 |
Transit
Downstream networks
Networks for which AS39572 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS214124 | Intrahost Solutions Ltd | Unclassified | IPv4 IPv6 | 2,405 |
| AS216070 | RCS Technologies FZE LLC | Unclassified | IPv4 IPv6 | 1,292 |
| AS60906 | Playdom B.V. | Unclassified | IPv4 IPv6 | 576 |
| AS44550 | Techno G Limited | Unclassified | IPv4 IPv6 | 368 |
| AS209929 | AWM LAB LTD | Unclassified | IPv4 IPv6 | 155 |
| AS21030 | Cluster LLC | Hosting | IPv4 | 124 |
| AS201024 | DATAWEB GLOBAL LP. | Unclassified | IPv4 | 119 |
| AS209366 | SEMrush CY LTD | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39572 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,698 |
| AS214124 | Intrahost Solutions Ltd | Unclassified | IPv4 IPv6 | 2,405 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,986 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,332 |
| AS216070 | RCS Technologies FZE LLC | Unclassified | IPv4 IPv6 | 1,292 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,289 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,210 |
| AS60906 | Playdom B.V. | Unclassified | IPv4 IPv6 | 576 |
| AS44550 | Techno G Limited | Unclassified | IPv4 IPv6 | 368 |
| AS209929 | AWM LAB LTD | Unclassified | IPv4 IPv6 | 155 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.