AS20533
Pjsc Vimpelcom — beeline.ru
Summary
Country |
![]() |
Organization | Pjsc Vimpelcom |
Domain | beeline.ru |
Number of IPv4 | 17,216 |
Number of IPv6 | 0 |
AS Type | ISP |
Registry | RIPE NCC |
Allocated | April 21, 2002 (about 23 years ago) |
Updated | July 21, 2021 (about 3 years ago) |
IP Ranges
AS20533 announces 61 IPv4 ranges and 0 IPv6 range.
That's a total of 17,216 IPv4 address and 0 IPv6 address.
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
89.188.224.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.225.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.226.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.227.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.228.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.229.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.230.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.231.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.232.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.233.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.234.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.235.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.236.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.237.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.238.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.239.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.240.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.241.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.242.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.243.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.244.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.245.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.246.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.247.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.248.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.249.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.250.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.251.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.252.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.253.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.254.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
89.188.255.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.224.0/21 |
![]() |
2,048 | RIPE NCC | ASSIGNED PA |
95.131.225.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.226.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.227.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.228.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.229.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.230.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
95.131.231.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
144.209.111.64/26 |
![]() |
64 | RIPE NCC | LEGACY |
185.123.172.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
185.123.173.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
185.123.174.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
185.123.175.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
217.148.192.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.193.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.194.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.195.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.196.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.197.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.198.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.199.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.200.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.201.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.202.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.203.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.204.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.205.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.206.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
217.148.207.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
Peers
AS20533 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
AS20533 connects to the global Internet via at least 1 upstream provider. In this setup, AS20533 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS20533 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.