Observed topology
AS48166 FORTEX-AS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS48166: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 256 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 87 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 85 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 51 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 45 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 18 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv6 | 15 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS48166 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57818 | SKTV Ltd. | Unclassified | IPv4 | 1,056 |
| AS57424 | Limited liability company "New Line" | Unclassified | IPv4 | 732 |
| AS59666 | FORTEX CJSC | Unclassified | IPv4 | 252 |
| AS197460 | Zencom LTD | Unclassified | IPv4 | 176 |
| AS51547 | JOINT-STOCK COMPANY "TELEPORT TELECOM" | Unclassified | IPv4 | 130 |
| AS43993 | IronTelecom OU | Unclassified | IPv4 | 105 |
| AS49510 | TCV Ltd | Unclassified | IPv4 | 60 |
| AS208942 | Firma "Zdorovye" LLC. | Unclassified | IPv4 | 60 |
| AS44705 | Obyedinennye Nakhabinskie seti LLC | Unclassified | IPv4 | 48 |
| AS49320 | Golitsyno Telecom Ltd | Residential | IPv4 | 48 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48166 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,273 |
| AS57818 | SKTV Ltd. | Unclassified | IPv4 | 1,056 |
| AS57424 | Limited liability company "New Line" | Unclassified | IPv4 | 732 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 522 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 512 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 368 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 298 |
| AS59666 | FORTEX CJSC | Unclassified | IPv4 | 252 |
| AS197460 | Zencom LTD | Unclassified | IPv4 | 180 |
| AS51547 | JOINT-STOCK COMPANY "TELEPORT TELECOM" | Unclassified | IPv4 | 130 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.