Observed topology
AS3216 SOVAM-AS
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3216: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,906 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,097 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3,013 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,528 |
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 1,711 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 1,515 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 657 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 591 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 540 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 374 |
Transit
Downstream networks
Networks for which AS3216 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8402 | PJSC "Vimpelcom" | Residential | IPv4 | 22,521 |
| AS16345 | PJSC "Vimpelcom" | Unclassified | IPv4 IPv6 | 11,043 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 | 6,043 |
| AS20533 | PJSC "Vimpelcom" | Unclassified | IPv4 | 3,658 |
| AS21332 | PJSC "Vimpelcom" | Unclassified | IPv4 | 3,658 |
| AS12418 | Quantum CJSC | Unclassified | IPv4 | 3,200 |
| AS15493 | "Russian company" LLC | Unclassified | IPv4 | 2,363 |
| AS49505 | JSC Selectel | Hosting | IPv4 | 2,054 |
| AS29125 | PJSC "Vimpelcom" | Unclassified | IPv4 | 1,888 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 | 1,736 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3216 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 70,565 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 59,531 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 37,877 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 25,295 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 IPv6 | 24,288 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 24,136 |
| AS8402 | PJSC "Vimpelcom" | Residential | IPv4 | 22,735 |
| AS48185 | team.blue NV | Unclassified | IPv4 | 20,260 |
| AS35168 | TNS-Plus LLP | Unclassified | IPv4 IPv6 | 18,959 |
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 18,936 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.