Data as of Nov 7, 2026
212.46.192.0/18
206 residential-proxy exits · 30 daysPJSC 'Vimpelcom'
Residential-proxy exits
Proxy exits
206
1.3% of its addresses · 30 days
Always-on exits
22
11% of its exits
Spread
55 of 64
/24s with at least one exit
Providers
90
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
48K observations
- Residential
- Business
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.46.217.0/24 since Mar 2012 | AS35102 | Business | PJSC "Vimpelcom" | ||
| 212.46.218.0/24 since Sep 2016 | AS3216 | Residential | 47 | PJSC "Vimpelcom" |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.46.192.0/18 | 16,384 | RU-SOVINTEL-980821 | PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU | ALLOCATED PA | — | abuse-b2b@ |
| └ 212.46.192.0/24 | 256 | RU-EDN-SOVINTEL-p2p-Static-Customer-IP-pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Feb 2, 2016 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.193.0/24 | 256 | RU-CITYLINE-FTTB-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN et CITY LINE | ASSIGNED PA | Oct 27, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.194.0/24 | 256 | RU-EDN-SOVINTEL-Clients-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Dec 7, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.0/29 | 8 | RU-SOVINTEL-MSK-eNeRGia-NTC-NET | 111024 Russia Moscow, ZC-5187785 | ASSIGNED PA | Nov 30, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.16/29 | 8 | RU-SOVINTEL-MSK-TDS-PRODAKTION-NET | 120170 Russia Moscow, ZC- 10006436 | ASSIGNED PA | Nov 30, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.24/29 | 8 | RU-SOVINTEL-MSK-A101-NET | 108802 Russia Moscow, ZC-22177004 | ASSIGNED PA | Nov 30, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.32/29 | 8 | RU-SOVINTEL-IZV-PeTRoiNTRaDe-NET | 426011 Russia Izhevsk, ZC-5192159 | ASSIGNED PA | Nov 30, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.40/29 | 8 | RU-SOVINTEL-MSK-FAO-DLya-SVyaZy-NET | unknown | ASSIGNED PA | Mar 16, 2017 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.48/28 | 16 | RU-BeeLine-MSK-RAEX-ANaLyTiCS-NET | 127006 Russia Moscow, ZC- 20545759 | ASSIGNED PA | Oct 4, 2024 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.64/27 | 32 | RU-SOVINTEL-MSK-RoSKoSMoS-NET | 107996 Russia Moscow, ZC-5198603 | ASSIGNED PA | Dec 2, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.168/29 | 8 | RU-SOVINTEL-MSK-B2B-SaNoFy-RuS-NET | 111250 Russia SOVINTEL/EDN, ZC-20165308 | ASSIGNED PA | Mar 10, 2016 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.195.184/29 | 8 | RU-SOVINTEL-MSK-TAYRAY-NET | 119435 Russia Moscow, ZC-5210910 | ASSIGNED PA | Dec 7, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.196.0/24 | 256 | RU-ViMPeLCoM-REG-Static-IP-Pool-NET | Russia Regions SOVINTEL/EDN | ASSIGNED PA | Dec 13, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.197.0/24 | 256 | RU-SOVAM-MSK-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Dec 14, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.198.0/24 | 256 | RU-GoldenTelecom-REG-Static-IP-Pool-NET | Russia Regions SOVINTEL/EDN | ASSIGNED PA | Dec 14, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.199.0/24 | 256 | RU-EDN-SOVINTEL-et-CITYLINE-IP-pool-p2p-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Dec 18, 2018 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.200.0/24 | 256 | RU-SOVAM-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Dec 21, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.201.0/24 | 256 | RU-SOVAM-REG-p2p-Static-IP-Pool-NET | Russia Regions SOVINTEL/EDN | ASSIGNED PA | Dec 21, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.202.0/24 | 256 | RU-SOVINTEL-EDN-B2B-client-pool-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Sep 19, 2023 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.203.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Dec 22, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.204.0/24 | 256 | RU-SOVINTEL-VLG-p2p-Static-IP-Pool-NET | 400001 Russia VolgoGrad SOVINTEL/EDN | ASSIGNED PA | Dec 27, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.205.0/24 | 256 | RU-CITY-LINE-B2B-Client-IP-PooL-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Jun 17, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.207.0/24 | 256 | RU-ViMPeLCoM-p2p-Static-IP-Pool-NET | Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Nov 22, 2011 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.208.0/24 | 256 | RU-SOVINTEL-K-p2p-Static-IP-Pool-NET | 610000 Russia SOVINTEL/EDN | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.209.0/26 | 64 | RU-SOVINTEL-KRV-p2p-Static-IP-Pool-NET | 610000 Russia Kirov SOVINTEL/EDN | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.209.64/26 | 64 | RU-SOVINTEL-SRT-p2p-Static-IP-Pool-NET | 610000 Russia Saratov and Penza Region SOVINTEL/EDN | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.210.0/24 | 256 | RU-CITY-LINE-p2p-client-IP-pool-NET | 111250 Russia SOVINTEL/EDN et CITY LINE | ASSIGNED PA | Mar 15, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.211.0/24 | 256 | RU-CITYLINE-p2p-endusers-static-IP-pool-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Sep 29, 2014 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.213.0/24 | 256 | RU-SOVINTEL-Static-Clients-IP-Pool-NET | Russia SOVINTEL/EDN | ASSIGNED PA | Sep 26, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.214.0/24 | 256 | RU-SOVAM-CityLine-Customers-IP-Pool-NET | 111250 Russia SOVINTEL/EDN et CityLine | ASSIGNED PA | Apr 25, 2017 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.215.0/24 | 256 | RU-CityLine-Static-IP-pool-NET | 111250 Russia Moscow SOVINTEL/EDN et CityLine | ASSIGNED PA | Jun 9, 2015 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.216.0/24 | 256 | RU-SOVINTEL-p2p-clients-IP-Pool-NET | 111250 Russia, Moscow Golden TeleCom et Sovam Teleport | ASSIGNED PA | Sep 18, 2013 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.217.0/24 | 256 | RU-SOVINTEL-MSK-Russian-Standard-Bank-NET | 105187 Russia Moscow, ZC-5289223 | ASSIGNED PA | Feb 13, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.218.0/24 | 256 | RU-SovamTelePort-MSK-BeeLine-Wi-Fi-NET | 111250 Russia Moscow SOVINTEL/EDN et SovamTelePort | ASSIGNED PA | Dec 24, 2013 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.219.0/25 | 128 | RU-SOVINTEL-p2p-and-clients-IP-Pool-NET | 111250 Russia SOVINTEL / EDN | ASSIGNED PA | Feb 14, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.219.128/25 | 128 | RU-SOVINTEL-SRT-p2p-and-clients-IP-Pool-NET | 410000 Russia Saratov SOVINTEL/EDN | ASSIGNED PA | Feb 14, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.220.0/24 | 256 | RU-SOVINTEL-MSK-p2p-and-clients-IP-Pool-NET | 11250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Feb 15, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.0/26 | 64 | RU-SOVINTEL-RZN-p2p-and-xDSL-IP-Pool-NET | 390006 Russia Ryazan SOVINTEL/EDN | ASSIGNED PA | Feb 16, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.64/26 | 64 | RU-EDN-SOVINTEL-p2p-et-xDSL-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Feb 16, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.128/26 | 64 | RU-SOVINTEL-IJV-p2p-and-xDSL-IP-Pool-NET | 426000 Russia Ijevsk SOVINTEL/EDN | ASSIGNED PA | Feb 17, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.192/27 | 32 | RU-SOVINTEL-EDN-p2p-et-B2B-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Feb 17, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.224/29 | 8 | RU-SOVINTEL-MSK-Belva-PTK-NET | 115230 Russia Moscow, ZC-5375405 | ASSIGNED PA | Feb 21, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.232/29 | 8 | RU-SOVINTEL-MSK-RNIMU-im-Pyrogova-NET | 117997 Russia Moscow, ZC-7319010 | ASSIGNED PA | Feb 21, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.240/29 | 8 | RU-SOVINTEL-MSK-SKTBE-NET | 129226 Russia Moscow, ZC- 12719443 | ASSIGNED PA | Feb 22, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.221.248/29 | 8 | RU-SOVINTEL-MSK-PaRTNeRPRoGRaMM-NET | 101203 Russia Moscow, ZC-5382072 | ASSIGNED PA | Feb 22, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.222.0/24 | 256 | RU-EDN-SOVINTEL-p2p-et-B2B-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jun 18, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.224.0/25 | 128 | RU-SOVINTEL-HBR-p2p-Static-IP-Pool-NET | 680000 Russia Habarovsk SOVINTEL/EDN | ASSIGNED PA | Feb 20, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.224.128/26 | 64 | RU-SOVINTEL-IVN-p2p-Static-IP-Pool-NET | 153000 Russia Ivanovo SOVINTEL/EDN | ASSIGNED PA | Apr 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.224.192/26 | 64 | RU-SOVINTEL-B2B-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.225.0/24 | 256 | RU-SOVINTEL-p2p-Static-IP-Pool-NET | 115114 Russia Moscow, SOVINTEL/EDN | ASSIGNED PA | May 17, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.226.0/24 | 256 | RU-SOVINTEL-MSK-p2p-and-xDSL-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Feb 22, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.227.0/24 | 256 | RU-SOVINTEL-VLG-p2p-and-xDSL-IP-Pool-NET | 400000 Russia VolgoGrad SOVINTEL/EDN | ASSIGNED PA | Feb 24, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.228.0/25 | 128 | RU-SOVINTEL-xDSL-et-p2p-static-pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jul 8, 2013 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.229.0/25 | 128 | RU-CITY-LINE-FTTB-Client-IP-PooL-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Jun 20, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.229.128/26 | 64 | RU-SOVINTEL-KSR-B2B-client-IP-Pool-NET | 156000 Russia Kostroma SOVINTEL/EDN | ASSIGNED PA | Mar 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.229.192/26 | 64 | RU-SOVINTEL-VRN-p2p-client-IP-Pool-NET | 394000 Russia Voronej SOVINTEL/EDN | ASSIGNED PA | Mar 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.230.0/24 | 256 | RU-CITY-LINE-B2B-clients-NET | 111250 Russia SOVINTEL/EDN et CITY LINE | ASSIGNED PA | Oct 2, 2001 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.231.0/24 | 256 | RU-SOVINTEL-MSK-xDSL-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Mar 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.232.0/24 | 256 | RU-SOVINTEL-MSK-FTTB-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Mar 2, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.233.0/25 | 128 | RU-CITY-LINE-p2p-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN et CITYLINE | ASSIGNED PA | Mar 5, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.233.128/25 | 128 | RU-SOVINTEL-KRD-FTTB-Static-IP-Pool-NET | 350000 Russia KrasNoDar SOVINTEL/EDN | ASSIGNED PA | Mar 5, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.234.0/25 | 128 | RU-BeeLine-B2B-client-IP-pool-NET | 111250 Russia SOVINTEL/EDN et SovAm Teleport | ASSIGNED PA | Jun 6, 2025 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.234.128/25 | 128 | RU-SOVINTEL-KRD-Static-IP-Pool-NET | 350000 Russia KrasNoDar SOVINTEL/EDN | ASSIGNED PA | Sep 3, 2013 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.235.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Mar 13, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.236.128/26 | 64 | RU-SOVINTEL-BRN-p2p-Static-IP-Pool-NET | 656000 Russia BarNaul SOVINTEL/EDN | ASSIGNED PA | Apr 10, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.237.0/24 | 256 | RU-SOVINTEL-EDN-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Mar 15, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.238.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Mar 23, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.239.64/28 | 16 | RU-BeeLine-KLG-GRaPe-NET | 248008 Russia Kaluga, ZC- 20308813 | ASSIGNED PA | Mar 26, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.239.84/30 | 4 | RU-SOVINTEL-MSK-Irbis-NET | unknown | ASSIGNED PA | Apr 12, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.239.88/29 | 8 | RU-SOVINTEL-MSK-SOLID-NET | 123007 Russia Moscow, ZC-5477235 | ASSIGNED PA | Apr 4, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.240.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 4, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.241.0/24 | 256 | RU-EDN-SOVINTEL-Static-client-IP-pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Apr 24, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.242.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 4, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.243.0/24 | 256 | RU-SOVINTEL-NSK-Static-Clients-IP-Pool-NET | Russia NovoSibirsk SOVINTEL/EDN | ASSIGNED PA | Oct 9, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.244.0/24 | 256 | RU-EDN-SOVINTEL-NETWORK-EQUIPMENT-IP-pool-NET | 111250 Russia EDN/SOVINTEL | ASSIGNED PA | Apr 13, 2018 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.0/28 | 16 | RU-SOVINTEL-MSK-Gables-Holdings-NET | 100147 Russia Moscow, ZC-5484080 | ASSIGNED PA | Apr 6, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.32/29 | 8 | RU-SOVINTEL-MSK-Sokol-IK-NET | 125167 Russia Moscow, ZC-6939670 | ASSIGNED PA | May 17, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.40/29 | 8 | RU-SOVINTEL-MSK-TECHCITY-DEV | 105120 Russia Moscow, ZC- 14684087 | ASSIGNED PA | Apr 13, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.48/29 | 8 | RU-Beeline-VLD-PRoMRuKaV-NET | 601273 Russia Vladimir, ZC- 12816982 | ASSIGNED PA | Apr 12, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.56/29 | 8 | RU-SOVINTEL-MSK-NIB-NET | 111345 Russia Moscow, ZC- 11844752 | ASSIGNED PA | Apr 13, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.128/26 | 64 | RU-SOVINTEL-IRK-p2p-Static-IP-Pool-NET | 664000 Russia Irkutsk SOVINTEL/EDN | ASSIGNED PA | May 18, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.245.192/26 | 64 | RU-SOVINTEL-MSK-MTK-NET | 127015 Russia Moscow, ZC-5554617 | ASSIGNED PA | Dec 6, 2013 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.246.0/25 | 128 | RU-CITY-LINE-p2p-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN et CITYLINERU | ASSIGNED PA | Apr 10, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.246.128/25 | 128 | RU-SOVINTEL-INFRA-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 10, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.247.0/24 | 256 | RU-SOVINTEL-MSK-p2p-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 10, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.248.0/24 | 256 | RU-SOVINTEL-REG-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Jun 7, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212. | 136 | RU-SOVINTEL-EDN-B2B-client-pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Mar 22, 2023 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.249.144/28 | 16 | RU-SOVINTEL-MSK-QUINTA-CFPITAL-NET | 125009 Russia Moscow, ZC- 11167526 | ASSIGNED PA | Sep 25, 2017 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.249.160/28 | 16 | RU-SOVINTEL-MSK-InterRAO-NET | 125047 Russia Moscow, ZC-5513640 | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.249.176/28 | 16 | RU-SOVINTEL-MSK-TeHNo-PRo-NET | 121357 Russia Moscow, ZC- 13541891 | ASSIGNED PA | Apr 22, 2021 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.249.192/26 | 64 | RU-SOVINTEL-EDN-B2B-client-pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Mar 22, 2023 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.250.0/24 | 256 | RU-SOVINTEL-MSK-MGMT-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.251.0/24 | 256 | RU-SOVINTEL-MSK-Clients-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 19, 2012 | abuse-b2b@ |
| └ 212.46.252.0/25 | 128 | RU-SOVINTEL-HBR-p2p-Static-IP-Pool-NET | 680000 Russia HubArovsk SOVINTEL/EDN | ASSIGNED PA | Apr 25, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.252.128/25 | 128 | RU-SOVINTEL-p2p-Static-IP-Pool-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Apr 25, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.253.0/24 | 256 | RU-SOVINTEL-MSK-p2p-et-Static-IP-Pool-NET | 111250 Russia Moscow SOVINTEL/EDN | ASSIGNED PA | Apr 27, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.254.0/24 | 256 | RU-SoViNTeL-eDN-B2B-Client-NET | 111250 Russia SOVINTEL/EDN | ASSIGNED PA | Jun 3, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.255.0/25 | 128 | RU-SOVINTEL-STP-p2p-Static-IP-Pool-NET | 355000 Russia StavroPol SOVINTEL/EDN | ASSIGNED PA | May 14, 2012 | abuse-b2b@ via RU-SOVINTEL-980821 |
| └ 212.46.255.128/25 | 128 | RU-CITY-LINE-Static-client-IP-pool-NET | 111250 Russia SOVINTEL/EDN et CITY LINE | ASSIGNED PA | Mar 15, 2019 | abuse-b2b@ via RU-SOVINTEL-980821 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 14,836 | 91% | 18 | |
| Business | 1,548 | 9.4% | 31 |
Network & registry
Origin network
AS3216
RU
- Name
- PJSC 'Vimpelcom'
- Type
- Internet provider
- Registered
- Apr 15, 1994
- Domain
- beeline.ru
- Website
- beeline.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
- VPN servers
- 4
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2005 · 21 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS3216 | RIPE | SOVINTEL/END broadband internet | SOVINTEL-MNT AS3216-MNT | Apr 28, 2012 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 212.46.192.0/24 | AS16345 | RIPE | PJSC "VimpelCom" | AS3216-MNT | Sep 11, 2019 |
| 212.46.193.0/24 | AS3216 | RIPE | VympelKom broadband internet | CITYLINERU-MNT | Oct 27, 2011 |
| 212.46.196.0/22 | AS3216 | RIPE | VympelKom broadband internet | CITYLINERU-MNT | Dec 13, 2011 |
| 212.46.200.0/22 | AS3216 | RIPE | SOVINTEL/EDN broadband internet | CITYLINERU-MNT | Dec 21, 2011 |
| 212.46.206.0/24 | AS16345 | RIPE | PJSC "VimpelCom" | AS3216-MNT | Sep 11, 2019 |
| 212.46.207.0/24 | AS3216 | RIPE | VympelKom broadband internet | CITYLINERU-MNT | Nov 22, 2011 |
| 212.46.227.0/24 | AS3216 | RIPE | PJSC VimpelCom, Russia, Moscow | AS3216-MNT | Jan 16, 2019 |
| 212.46.230.0/24 | AS3216 | RIPE | PJSC VimpelCom, Russia, Moscow | AS3216-MNT | Jan 10, 2019 |
| 212.46.243.0/24 | AS3216 | RIPE | VimpelCom | AS3216-MNT | May 3, 2012 |
Whois
Registration for this announcement
- Range
- 212.
46. 192. 0/ 18 - Netname
- RU-SOVINTEL-980821
- Registrant
- PJSC "Vimpelcom"
- Registrant country
- RU
- Organization
- PJSC "Vimpelcom" (ORG-ES15-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Not stated by the registry
- Updated
- Oct 27, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Aug 21, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse-b2b@
beeline. ru - Name
- Sovintel Abuse Department
- Handle
- SVNT2-RIPE