Observed topology
AS16143 RADIONET-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS16143: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 114 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 90 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 86 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 49 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 48 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 36 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 26 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS16143 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43168 | Singer-Computer Ltd. | Unclassified | IPv4 | 232 |
| AS61068 | OOO "NECSTEL" | Residential | IPv4 | 63 |
| AS196667 | Apeks Security Ltd | Unclassified | IPv4 | 59 |
| AS204357 | AGR LLC | Unclassified | IPv4 | 59 |
| AS61435 | JSC Arkhbum | Unclassified | IPv4 | 43 |
| AS213403 | Kairos Ltd. | Unclassified | IPv4 | 42 |
| AS199126 | Pikhta Bank LLC | Unclassified | IPv4 | 29 |
| AS49053 | LLC Wildberries | Unclassified | IPv4 | 7 |
| AS51780 | FGBU VNIIKR | Unclassified | IPv4 | 2 |
| AS198261 | Ltd InTelCom-TG | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16143 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 399 |
| AS43168 | Singer-Computer Ltd. | Unclassified | IPv4 | 232 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 178 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 107 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 90 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 68 |
| AS61068 | OOO "NECSTEL" | Residential | IPv4 | 63 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 63 |
| AS196667 | Apeks Security Ltd | Unclassified | IPv4 | 59 |
| AS204357 | AGR LLC | Unclassified | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.