Data as of Nov 21, 2026
212.48.32.0/19
23 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
23
0.28% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Spread
13 of 32
/24s with at least one exit
Providers
76
selling exits here
Oct 22, 2026 – Nov 20, 2026
Exits seen per day
6.0K observations
- Mobile
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.48.46.0/24 | 1 | 3 | |
| 212.48.55.0/24 | 0 | 3 | |
| 212.48.35.0/24 | 0 | 3 | |
| 212.48.62.0/24 | 0 | 3 | |
| 212.48.38.0/24 | 0 | 2 | |
| 212.48.63.0/24 | 0 | 2 | |
| 212.48.43.0/24 | 0 | 1 | |
| 212.48.56.0/24 | 0 | 1 | |
| 212.48.57.0/24 | 0 | 1 | |
| 212.48.58.0/24 | 0 | 1 | |
| 212.48.60.0/24 | 0 | 1 | |
| 212.48.47.0/24 | 0 | 1 | |
| 212.48.34.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9HTTP
- 9Proxy
- AETHYN_BASIC
- Ake.net
- B2Proxy
- BUYPERSONALPROXY
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- Byteful
- CYBERYOZH
- CatProxies
- CliProxy
- DataImpulse
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLAMEPROXIES_BASIC
- FastProxy
- FloppyData
- GEEKPROXY_TURBO
- Geonode
- GhostConnect
- HASDATA
- HPROXY
- HideProxy
- IPFly
- IPMUSK
- IPRoyal
- InfiniteProxies
- KindProxy
- Kookey
- LudaxProxy
- NSocks
- NextProxy
- NovaProxy
- Novada
- PROXIWARE_ECO
- PROXYFALL
- PROXYON
- PROXYSALE
- PROXYSAVER
- PROXYSCRAPE
- PROXY_CC
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxiware
- Proxmint
- Proxy302
- Proxy4U
- ProxyGeo
- ProxyRack
- ProxyWing
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- SPYDERPROXY_BASIC
- Shifter
- Smartproxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
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.48.32.0/19 | 8,192 | RU-MTU-20020606 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Jun 11, 2002 | abuse@ |
| └ 212.48.49.48/30 | 4 | Komus | LLC "Komus" | ASSIGNED PA | Aug 8, 2011 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.56/30 | 4 | Avangard-spetsodezhda3_ | Avangard-spetsodezhda3 | ASSIGNED PA | Mar 13, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.60/30 | 4 | Angstrem-Service2_ | Angstrem-Service2 | ASSIGNED PA | Mar 20, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.64/30 | 4 | Pervoe_ | Bank "Pervoe OBK" | ASSIGNED PA | Feb 2, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.92/30 | 4 | NORDBLOM2_ | NORDBLOM | ASSIGNED PA | Feb 9, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.108/30 | 4 | MAIZ2_ | MAIZ | ASSIGNED PA | Feb 12, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.140/30 | 4 | Almaz_ | Almaz group | ASSIGNED PA | Feb 18, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.152/30 | 4 | Amalit_ | Amalit | ASSIGNED PA | Feb 20, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.176/30 | 4 | Dekoteks-2000_ | Dekoteks-2000 | ASSIGNED PA | Feb 25, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.180/30 | 4 | Uniline2_ | Uniline | ASSIGNED PA | Mar 2, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.184/30 | 4 | VSK-MOSCOW2_ | unknown | ASSIGNED PA | Apr 12, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.188/30 | 4 | Zemskaya_ | Zemskaya TEK | ASSIGNED PA | Apr 12, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.192/30 | 4 | Telmos_ | Telmos JSC | ASSIGNED PA | Mar 5, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.49.240/29 | 8 | Tehprokomplekt2_ | Tehprokomplekt | ASSIGNED PA | Oct 31, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.4/30 | 4 | Avantag_ | Avantag & K | ASSIGNED PA | Mar 15, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.16/29 | 8 | Zebratelecom1_ | Zebratelecom | ASSIGNED PA | Mar 11, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.24/29 | 8 | Morgan_ | LLC "Morgan Stanley Bank" | ASSIGNED PA | Jun 9, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.32/29 | 8 | Strakh_ | Strakh | ASSIGNED PA | Jun 21, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.48/30 | 4 | Paradis_ | Paradis XXI | ASSIGNED PA | Feb 21, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.64/30 | 4 | CT-Media_ | CT-Media | ASSIGNED PA | Feb 10, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.76/30 | 4 | Viakom_ | Viakom | ASSIGNED PA | Mar 23, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.80/29 | 8 | SSC1_ | SSC | ASSIGNED PA | Mar 23, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.96/30 | 4 | AmericanCityPizza714_ | American City Pizza | ASSIGNED PA | Mar 24, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.104/30 | 4 | Victorya_ | Victorya Andreanova | ASSIGNED PA | Mar 26, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.108/30 | 4 | ALDAN-U1_ | unknown | ASSIGNED PA | Mar 29, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.112/29 | 8 | NC-BANK | Commers Bank «NC BANK » | ASSIGNED PA | Mar 29, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.120/30 | 4 | Kirsanov_ | Kirsanov | ASSIGNED PA | Apr 14, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.128/30 | 4 | SportStroyInvestNet | SportStroyInvest | ASSIGNED PA | Mar 30, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.144/29 | 8 | Lucksness14_ | Lucksness food | ASSIGNED PA | Apr 14, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.152/30 | 4 | Speranca-M_ | Speranca-M Trading | ASSIGNED PA | Apr 7, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.164/30 | 4 | Avangard-spetsodezhda2_ | Avangard-spetsodezhda2 | ASSIGNED PA | Dec 12, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.172/30 | 4 | Lucksness_ | Lucksness food | ASSIGNED PA | Dec 2, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.184/30 | 4 | Business_ | Business Autograd LLC | ASSIGNED PA | Apr 13, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.200/30 | 4 | EKA2_ | EKA | ASSIGNED PA | Dec 8, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.212/30 | 4 | Bonshans-M_ | Bonshans-M | ASSIGNED PA | Apr 15, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.232/30 | 4 | Universe_ | The Universe Of Beauty | ASSIGNED PA | Dec 10, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.50.248/30 | 4 | Tehnokom_ | Tehnokom | ASSIGNED PA | Mar 28, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.0/29 | 8 | Manege1_ | Manege | ASSIGNED PA | Apr 22, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.8/30 | 4 | Vostokhim_ | Vostokhim | ASSIGNED PA | Feb 28, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.24/30 | 4 | Velant_ | Velant Consulting | ASSIGNED PA | Apr 27, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.28/30 | 4 | AmericanCityPizza146_ | American City Pizza | ASSIGNED PA | Jan 18, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.36/30 | 4 | TREST_ | TREST "B" ó.A | ASSIGNED PA | Feb 8, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.44/30 | 4 | Elektronie_ | Elektronie tablo | ASSIGNED PA | Apr 29, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.60/30 | 4 | ARss2_ | ARss2 | ASSIGNED PA | Feb 3, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.76/30 | 4 | Yahont_ | Yahont | ASSIGNED PA | May 17, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.88/30 | 4 | Adzuro_ | Adzuro | ASSIGNED PA | May 18, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.96/29 | 8 | Victorya_ | Victorya Andreanova | ASSIGNED PA | May 19, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.108/30 | 4 | AZOCM_ | AZOCM | ASSIGNED PA | Jun 29, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.112/30 | 4 | Barry-Callebaut_ | Barry-Callebaut | ASSIGNED PA | May 21, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.128/30 | 4 | Ruspel_ | Ruspel | ASSIGNED PA | May 28, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.156/30 | 4 | Rek-2000_ | Rek-2000 | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.160/30 | 4 | Progres_ | Progres | ASSIGNED PA | May 4, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.164/30 | 4 | DGI_ | unknown | ASSIGNED PA | Jan 21, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.188/30 | 4 | PENTA_ | Penta Travel | ASSIGNED PA | Jun 8, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.192/30 | 4 | ComSav_ | ComSav | ASSIGNED PA | Jun 8, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.208/30 | 4 | VV-stroiinvest_ | VV-stroiinvest | ASSIGNED PA | Jun 10, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.224/30 | 4 | Medical_ | Medical center | ASSIGNED PA | Jun 17, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.228/30 | 4 | Trade_ | Trade house Vinogradov and K | ASSIGNED PA | Jul 19, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.240/30 | 4 | Connect-st_ | Connect-st | ASSIGNED PA | Apr 22, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.51.244/30 | 4 | Unikon_ | Unikon | ASSIGNED PA | Jun 23, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.52.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 3, 2020 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.0/30 | 4 | ITEK2_ | ITEK | ASSIGNED PA | Aug 4, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.4/30 | 4 | Moneti_ | Moneti I medali | ASSIGNED PA | Aug 25, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.8/30 | 4 | Promelectrosnab_ | Promelectrosnab | ASSIGNED PA | Aug 31, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.24/30 | 4 | Varshavka-USN_ | Varshavka-USN LLC | ASSIGNED PA | Sep 1, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.52/30 | 4 | VIP_ | VIP Service | ASSIGNED PA | Feb 10, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.68/30 | 4 | Office_ | Office AGNS | ASSIGNED PA | Sep 10, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.72/30 | 4 | FKU-GB-MSE-pogMoskve-Mintruda-Rossii | FKU GB MSE pog Moskve Mintruda Rossii | ASSIGNED PA | Sep 22, 2021 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.76/30 | 4 | GBUMSE-NET | Fgup "Gbumse" | ASSIGNED PA | Apr 17, 2020 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.84/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jun 6, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.88/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | May 19, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.92/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Mar 3, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.96/30 | 4 | Tehprokomplekt_ | Tehprokomplekt | ASSIGNED PA | Sep 14, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.100/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Sep 14, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.120/30 | 4 | Zara_ | The limited liability company "Zara Home CIS" | ASSIGNED PA | Feb 6, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.144/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 30, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.148/30 | 4 | GALA_ | LLC "Gala Pizza" | ASSIGNED PA | Jan 30, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.152/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 30, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.156/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 24, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.160/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 24, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.164/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 19, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.184/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 19, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.188/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 19, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.192/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 19, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.196/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.200/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.208/30 | 4 | TOUR-Centre | LLC "TOUR-Centre" | ASSIGNED PA | Aug 26, 2005 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.212/30 | 4 | Arsenal_ | Arsenal Spets Tehnika | ASSIGNED PA | Oct 6, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.216/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.224/30 | 4 | Nebolit2_ | Nebolit | ASSIGNED PA | Oct 15, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.228/30 | 4 | Vektor_ | Vektor z | ASSIGNED PA | Oct 18, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.232/30 | 4 | Seneks_ | Seneks | ASSIGNED PA | Oct 18, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.236/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.240/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.244/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.248/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 16, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.53.252/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Nov 1, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.0/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.8/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.12/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.16/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.20/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.24/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.28/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.32/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.36/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 11, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.44/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 29, 2016 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.48/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.52/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Nov 22, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.56/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Nov 24, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.60/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Dec 10, 2004 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.64/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.68/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.72/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.76/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.80/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.84/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.92/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.96/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.100/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.104/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.108/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.112/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.116/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.120/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.124/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.128/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.132/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.136/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.140/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.144/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.148/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.152/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.156/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.164/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 10, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.168/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.172/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.176/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.180/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.184/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.188/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.196/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.200/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.208/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.212/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.216/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.220/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.224/28 | 16 | Lohin_ | Lohin | ASSIGNED PA | Apr 12, 2006 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.240/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.244/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.248/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.54.252/30 | 4 | GBUMSE-NET | Fgup «gbumse» | ASSIGNED PA | Jan 13, 2017 | abuse@ via RU-MTU-20020606 |
| └ 212.48.55.0/24 | 256 | Customers_ | Customer's P2P WAN Interfaces | ASSIGNED PA | Oct 1, 2003 | abuse@ via RU-MTU-20020606 |
| └ 212.48.57.0/24 | 256 | Customers_ | PJSC MTS | ASSIGNED PA | Dec 4, 2020 | abuse@ via RU-MTU-20020606 |
| └ 212.48.58.0/24 | 256 | Customers_ | PJSC MTS | ASSIGNED PA | Dec 4, 2020 | abuse@ via RU-MTU-20020606 |
| └ 212.48.60.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 14, 2003 | abuse@ via RU-MTU-20020606 |
| └ 212.48.61.0/24 | 256 | Customers_ | Customer's P2P WAN Interfaces | ASSIGNED PA | Nov 19, 2007 | abuse@ via RU-MTU-20020606 |
| └ 212.48.62.0/24 | 256 | Customers_ | Customer's P2P WAN Interfaces | ASSIGNED PA | Nov 19, 2007 | abuse@ via RU-MTU-20020606 |
| └ 212.48.63.0/24 | 256 | Customers_ | Customer's P2P WAN Interfaces | ASSIGNED PA | Nov 19, 2007 | abuse@ via RU-MTU-20020606 |
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
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Mobile | 5,655 | 69% | 135 | |
| Business | 2,533 | 31% | 346 | |
| Residential | 4 | 0.05% | 1 |
Network & registry
Origin network
AS8359
RU
- Name
- MTS PJSC
- Type
- Internet provider
- Registered
- Jun 26, 1997
- Domain
- mts.ru
- Website
- ir.mts.ru/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2009 · 18 yr
- Origin networks
- 3
- Last change of origin
- May 2009
Recorded history
History
- Handoffs
- 2
Whois
Registration for this announcement
- Range
- 212.
48. 32. 0/ 19 - Netname
- RU-MTU-20020606
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jun 11, 2002
- Updated
- Sep 29, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jun 6, 2002
- Status
- assigned
Report abuse
Abuse contact
- abuse@
mtu. ru - Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE