Autonomous System details
AS16345
Pjsc Vimpelcom — beeline.ru
Summary
| Country |
 Russian Federation
|
| Organization | Pjsc Vimpelcom |
| Domain | beeline.ru |
| Number of IPv4 | 87,552 |
| Number of IPv6 | 8.1395× 1028 |
| AS Type | ISP |
| Registry | RIPE NCC |
| Allocated | June 21, 2002 (about 23 years ago) |
| Updated | November 21, 2022 (about 2 years ago) |
IP Ranges
AS16345 announces 141 IPv4 ranges and 23 IPv6 ranges.
That's a total of 87,552 IPv4 addresses and 8.1395× 1028 IPv6 addresses.
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 31.13.144.0/24 |
Mobile Core in Samara
|
256 | RIPE NCC | ASSIGNED PA |
| 31.13.145.0/24 |
Mobile Core in Samara
|
256 | RIPE NCC | ASSIGNED PA |
| 31.13.146.0/23 |
Apn STATIC.BEELINE.RU
|
512 | RIPE NCC | ASSIGNED PA |
| 31.13.148.0/22 |
Apn STATIC.BEELINE.RU
|
1,024 | RIPE NCC | ASSIGNED PA |
| 37.9.240.0/22 |
Apn STATIC.BEELINE.RU
|
1,024 | RIPE NCC | ASSIGNED PA |
| 37.9.244.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 37.9.245.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 37.9.246.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 37.9.247.0/24 |
Apn STATIC.BEELINE.RU
|
256 | RIPE NCC | ASSIGNED PA |
| 46.16.96.0/21 |
Apn STATIC.BEELINE.RU
|
2,048 | RIPE NCC | ASSIGNED PA |
| 46.250.52.0/22 |
Russia Moscow Vimpelcom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 77.41.190.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | LIR-PARTITIONED PA |
| 81.9.113.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 81.9.116.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 81.9.117.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 81.9.118.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 81.9.126.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 81.222.176.0/20 |
Pjsc Vimpelcom
|
4,096 | RIPE NCC | ALLOCATED PA |
| 81.222.176.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ALLOCATED PA |
| 81.222.180.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 81.222.182.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 81.222.184.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 81.222.186.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 81.222.188.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ALLOCATED PA |
| 81.222.218.0/23 |
Now Pao Vimpelcom - Formely Zao Eltel
|
512 | RIPE NCC | LIR-PARTITIONED PA |
| 83.220.224.0/24 |
Firewall Pool in Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.225.0/24 |
Firewall Pool in Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.226.0/24 |
Firewall Pool in Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.227.0/24 |
Firewall Pool in Spb
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.228.0/24 |
Vimpelcom Moscow International Gateway
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.229.0/24 |
Vimpelcom Saint-petersburg International Gateway
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.230.0/24 |
Vimpelcom Novosibirsk International Gateway
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.231.0/24 |
Vimpelcom Khabarovsk International Gateway
|
256 | RIPE NCC | ASSIGNED PA |
| 83.220.232.0/22 |
Apn STATIC.BEELINE.RU
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.220.236.0/22 |
Beeline-moscow Gprs Firewall
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.220.240.0/20 |
Apn STATIC.BEELINE.RU
|
4,096 | RIPE NCC | ASSIGNED PA |
| 85.115.234.0/24 |
Gprs Core Infrastruxture
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.235.0/24 |
Gprs Core Infrastruxture
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.236.0/22 |
Apn M2MSTATIC.BEELINE.RU
|
1,024 | RIPE NCC | ASSIGNED PA |
| 85.115.240.0/21 |
Gprs Core Infrastruxture
|
2,048 | RIPE NCC | ASSIGNED PA |
| 85.115.240.0/23 |
Gprs Core Infrastruxture
|
512 | RIPE NCC | ASSIGNED PA |
| 85.115.242.0/24 |
Beeline-moscow Grx Gprs Core
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.243.0/24 |
Gprs Core Infrastruxture
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.246.0/24 |
Beeline-moscow Gprs Firewall
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.248.0/24 |
Firewall Pool in Stavropol
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.249.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 85.115.252.0/22 |
Apn STATIC.BEELINE.RU
|
1,024 | RIPE NCC | ASSIGNED PA |
| 85.249.16.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 85.249.18.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 85.249.20.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ALLOCATED PA |
| 85.249.24.0/21 |
Pjsc Vimpelcom
|
2,048 | RIPE NCC | ALLOCATED PA |
| 85.249.160.0/20 |
Pjsc Vimpelcom
|
4,096 | RIPE NCC | ALLOCATED PA |
| 85.249.230.0/24 |
Edn Et Eltel
|
256 | RIPE NCC | ASSIGNED PA |
| 89.113.0.0/22 |
Pool for Static Ip-address Services for Mobile Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 89.113.4.0/22 |
Pool for Static Ip-address Services for Mobile Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 89.113.8.0/22 |
Pool for Static Ip-address Services for Mobile Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 89.113.12.0/22 |
Pool for Static Ip-address Services for Mobile Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 89.113.30.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ALLOCATED PA |
| 89.113.98.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 89.113.101.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 89.113.102.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 89.113.127.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 89.113.136.0/21 |
Pjsc Vimpelcom
|
2,048 | RIPE NCC | ALLOCATED PA |
| 89.113.144.0/21 |
Pjsc Vimpelcom
|
2,048 | RIPE NCC | ALLOCATED PA |
| 89.113.152.0/21 |
Pjsc Vimpelcom
|
2,048 | RIPE NCC | ALLOCATED PA |
| 91.193.176.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ASSIGNED PI |
| 109.197.200.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ASSIGNED PI |
| 109.197.204.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ASSIGNED PI |
| 176.15.162.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.163.0/24 |
16345 Region 78
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.164.0/23 |
16345 Region 78
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.166.0/23 |
16345 Region 78
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.173.0/24 |
16345 Region 06
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.174.0/24 |
16345 Region 15
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.175.0/24 |
16345 Region 95
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.176.0/23 |
16345 Region 23
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.178.0/24 |
16345 Region 05
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.179.0/24 |
16345 Region 07
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.180.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.181.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.182.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.183.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.184.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.185.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.186.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.187.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.188.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.189.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.190.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.191.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.192.0/21 |
Dynamic Ip Pool for Broadband Customers
|
2,048 | RIPE NCC | ASSIGNED PA |
| 176.15.200.0/21 |
Dynamic Ip Pool for Broadband Customers
|
2,048 | RIPE NCC | ASSIGNED PA |
| 176.15.208.0/21 |
Dynamic Ip Pool for Broadband Customers
|
2,048 | RIPE NCC | ASSIGNED PA |
| 176.15.218.0/23 |
Dynamic Ip Pool for Broadband Customers
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.220.0/22 |
Dynamic Ip Pool for Broadband Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.15.240.0/22 |
Dynamic Ip Pool for Broadband Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.15.244.0/23 |
Dynamic Ip Pool for Broadband Customers
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.246.0/23 |
Dynamic Ip Pool for Broadband Customers
|
512 | RIPE NCC | ASSIGNED PA |
| 176.15.248.0/22 |
Dynamic Ip Pool for Broadband Customers
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.15.252.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.253.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.254.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 176.15.255.0/24 |
Dynamic Ip Pool for Broadband Customers
|
256 | RIPE NCC | ASSIGNED PA |
| 188.65.241.0/24 |
Static Ip Pool Homeuser
|
256 | RIPE NCC | ASSIGNED PA |
| 188.65.242.0/23 |
Ip Static Pool
|
512 | RIPE NCC | ASSIGNED PA |
| 188.65.244.0/22 |
Static Ip Metroethernet Net
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.66.32.0/22 |
Osjc Severtranscom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 194.85.151.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 194.186.78.0/24 |
Russia Sovintel/edn Et Sovamteleport
|
256 | RIPE NCC | ASSIGNED PA |
| 194.186.221.0/24 |
Russia Sovintel/edn Et Beeline
|
256 | RIPE NCC | ASSIGNED PA |
| 195.209.160.0/23 |
Pjsc Vimpelcom
|
512 | RIPE NCC | ASSIGNED PA |
| 195.209.164.0/22 |
Pjsc Vimpelcom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 195.239.218.0/24 |
Russia Saint-petersburg Vimpelcom P2p
|
256 | RIPE NCC | ASSIGNED PA |
| 195.239.227.0/24 |
Russia Saint-petersburg Vimpelcom P2p
|
256 | RIPE NCC | ASSIGNED PA |
| 213.221.12.0/24 |
Tcpacc, 1c-11963174
|
256 | RIPE NCC | ASSIGNED PA |
| 213.234.222.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 213.234.251.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ALLOCATED PA |
| 217.118.64.0/24 |
JSC Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.65.0/24 |
JSC Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.66.0/24 |
JSC Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.67.0/24 |
JSC Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.68.0/22 |
JSC Vimpelcom Nn Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 217.118.72.0/22 |
JSC Vimpelcom Moscow Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 217.118.76.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.77.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.78.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.79.0/24 |
Pjsc Vimpelcom
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.80.0/24 |
JSC Vimpelcom Wlan1 Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.81.0/24 |
JSC Vimpelcom Wlan1 Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.82.0/24 |
JSC Vimpelcom Wlan1 Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.83.0/24 |
JSC Vimpelcom Wlan1 Moscow
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.84.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.85.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.86.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.87.0/24 |
Ojsc Vimpelcom Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.88.0/24 |
JSC Vimpelcom Moscow Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.89.0/24 |
JSC Vimpelcom Moscow Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.90.0/24 |
JSC Vimpelcom Moscow Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.91.0/24 |
JSC Vimpelcom Moscow Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.93.0/24 |
Firewall Pool in Nnovgorod
|
256 | RIPE NCC | ASSIGNED PA |
| 217.118.95.0/24 |
Firewall Pool in Voronezh
|
256 | RIPE NCC | ASSIGNED PA |
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 2a02:2668::/32 |
Bee6 Infra
|
7.9228× 1028 | RIPE NCC | ASSIGNED |
| 2a02:2668:3900::/40 |
BEE6 39
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
| 2a02:2668:5400::/40 |
BEE6 54
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
| 2a02:2668:6100::/40 |
BEE6 61
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
| 2a02:2668:6600::/40 |
BEE6 66
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
| 2a02:2668:7400::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7410::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7420::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7430::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7440::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7450::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7460::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7470::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7480::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7490::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74a0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74b0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74c0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74d0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74e0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:74f0::/44 |
BEE6 74
|
1.9343× 1025 | RIPE NCC | ASSIGNED |
| 2a02:2668:7500::/40 |
BEE6 76
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
| 2a02:2668:7600::/40 |
BEE6 76
|
3.0949× 1026 | RIPE NCC | ASSIGNED |
Peers
AS16345 does not have any direct peering agreements. Instead, its global connectivity is achieved through transit providers. While this setup ensures comprehensive reach, future peering could reduce latency and optimize route efficiency.
Upstreams
AS16345 connects to the global Internet via at least 2 upstream providers. In this setup, AS16345 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS16345 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.