Observed topology
AS399486 VIRTUO
Hosting DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS399486: 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 | 1,282 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 856 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 752 |
| AS46450 | Pilot Fiber, Inc. | Residential | IPv4 | 663 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 528 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 215 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 25 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 24 |
Transit
Downstream networks
Networks for which AS399486 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198831 | GENIUSWEER SAS | Hosting | IPv4 IPv6 | 2,517 |
| AS60900 | Adrian Trifonov trading as Ssmidge Technologies | Unclassified | IPv4 IPv6 | 491 |
| AS213535 | YottaSrc | Hosting | IPv4 IPv6 | 419 |
| AS400897 | PETROSKY CLOUD LLC | Unclassified | IPv4 | 409 |
| AS212720 | NET2LAN SASU | Unclassified | IPv4 IPv6 | 329 |
| AS395904 | Servury | Unclassified | IPv4 IPv6 | 182 |
| AS201744 | ByteFlare LTD | Unclassified | IPv4 | 174 |
| AS400596 | Technologies Elixior | Hosting | IPv4 IPv6 | 91 |
| AS402554 | FFxF | Unclassified | IPv4 IPv6 | 91 |
| AS210699 | WEDEPLOY SAS | Hosting | IPv4 IPv6 | 90 |
Adjacency
Adjacent networks
Every AS seen directly next to AS399486 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198831 | GENIUSWEER SAS | Hosting | IPv4 IPv6 | 4,413 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 2,970 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,942 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,513 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,472 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,135 |
| AS46450 | Pilot Fiber, Inc. | Residential | IPv4 | 688 |
| AS60900 | Adrian Trifonov trading as Ssmidge Technologies | Unclassified | IPv4 IPv6 | 589 |
| AS213535 | YottaSrc | Hosting | IPv4 IPv6 | 419 |
| AS400897 | PETROSKY CLOUD LLC | Unclassified | IPv4 | 409 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.