Data as of Nov 3, 2026
83.237.0.0/16
329 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
329
0.50% of its addresses · 30 days
Always-on exits
14
4.3% of its exits
Spread
177 of 256
/24s with at least one exit
Providers
99
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
47K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- Webshare
- YumiProxy
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 |
|---|---|---|---|---|---|---|
| 83.237.0.0/16 | 65,536 | RU-MTU-20040212 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Feb 12, 2004 | [email protected] |
| └ 83.237.0.0/24 | 256 | Customers_P2P_2023_27_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.1.0/24 | 256 | Customers_P2P_2023_28_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.2.0/24 | 256 | Customers_P2P_2023_29_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.3.0/24 | 256 | Customers_P2P_2023_30_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.4.0/24 | 256 | Customers_P2P_2023_31_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.5.0/24 | 256 | Customers_P2P_2023_32_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.6.0/24 | 256 | Customers_P2P_2023_33_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.7.0/24 | 256 | Customers_P2P_2023_34_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.8.0/24 | 256 | Customers_P2P_2023_35_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.9.0/24 | 256 | Customers_P2P_2023_36_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.10.0/24 | 256 | Customers_P2P_2023_37_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.11.0/24 | 256 | Customers_P2P_2023_38_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.12.0/24 | 256 | Customers_P2P_2023_39_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.13.0/24 | 256 | Customers_P2P_2023_40_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.14.0/24 | 256 | Customers_P2P_2023_41_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.15.0/24 | 256 | Customers_P2P_2023_42_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.16.0/24 | 256 | Customers_P2P_2023_43_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.17.0/24 | 256 | Customers_P2P_2023_44_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.18.0/24 | 256 | Customers_P2P_2023_45_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.19.0/24 | 256 | Customers_P2P_2024_00_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.20.0/24 | 256 | Customers_P2P_2024_01_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.21.0/24 | 256 | Customers_P2P_2024_02_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.22.0/24 | 256 | Customers_P2P_2024_03_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.23.0/24 | 256 | Customers_P2P_2024_04_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.24.0/24 | 256 | Customers_P2P_2024_05_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.25.0/24 | 256 | Customers_P2P_2024_06_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.26.0/24 | 256 | Customers_P2P_2024_07_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.27.0/24 | 256 | Customers_P2P_2024_08_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.28.0/24 | 256 | Customers_P2P_2024_09_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.29.0/24 | 256 | Customers_P2P_2024_10_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.30.0/24 | 256 | Customers_P2P_2024_11_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.31.0/24 | 256 | Customers_P2P_2024_12_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.32.0/24 | 256 | Customers_P2P_2024_13_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.33.0/24 | 256 | Customers_P2P_2024_14_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.34.0/24 | 256 | Customers_P2P_2024_15_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.35.0/24 | 256 | Customers_P2P_2024_16_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.36.0/24 | 256 | Customers_P2P_2024_17_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.37.0/24 | 256 | Customers_P2P_2024_18_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.38.0/24 | 256 | Customers_P2P_2024_19_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.39.0/24 | 256 | Customers_P2P_2024_20_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.40.0/24 | 256 | Customers_P2P_2024_21_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.41.0/24 | 256 | Customers_P2P_2024_22_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.42.0/24 | 256 | Customers_P2P_2024_23_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.43.0/24 | 256 | Customers_P2P_2024_24_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.44.0/24 | 256 | Customers_P2P_2024_25_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.45.0/24 | 256 | Customers_P2P_2024_26_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.46.0/24 | 256 | Customers_P2P_2024_27_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.47.0/24 | 256 | Customers_P2P_2024_28_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.48.0/24 | 256 | Customers_P2P_2024_29_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.49.0/24 | 256 | Customers_P2P_2024_30_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.50.0/24 | 256 | Customers_P2P_2024_31_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.51.0/24 | 256 | Customers_P2P_2024_32_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.52.0/24 | 256 | Customers_P2P_2024_33_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.53.0/24 | 256 | Customers_P2P_2024_34_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.54.0/24 | 256 | Customers_P2P_2024_35_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.55.0/24 | 256 | Customers_P2P_2024_36_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.56.0/24 | 256 | Customers_P2P_2024_37_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.57.0/24 | 256 | Customers_P2P_2024_38_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.58.0/24 | 256 | Customers_P2P_2024_39_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.59.0/24 | 256 | Customers_P2P_2024_40_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.60.0/24 | 256 | Customers_P2P_2024_41_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.61.0/24 | 256 | Customers_P2P_2024_42_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.62.0/24 | 256 | Customers_P2P_2024_43_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.63.0/24 | 256 | Customers_P2P_2024_44_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.64.0/24 | 256 | Customers_P2P_2024_45_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.65.0/24 | 256 | Customers_P2P_2024_46_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.66.0/24 | 256 | Customers_P2P_2024_47_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.67.0/24 | 256 | Customers_P2P_2024_48_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.68.0/24 | 256 | Customers_P2P_2024_49_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.69.0/24 | 256 | Customers_P2P_2024_50_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.70.0/24 | 256 | Customers_P2P_2024_51_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.71.0/24 | 256 | Customers_P2P_2024_52_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.72.0/24 | 256 | Customers_P2P_2024_53_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.73.0/24 | 256 | Customers_P2P_2024_54_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.74.0/24 | 256 | Customers_P2P_2024_55_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.75.0/24 | 256 | Customers_P2P_2024_56_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.76.0/24 | 256 | Customers_P2P_2024_57_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.77.0/24 | 256 | Customers_P2P_2024_58_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.78.0/24 | 256 | Customers_P2P_2024_59_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.79.0/24 | 256 | Customers_P2P_2024_60_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 27, 2024 | [email protected] via RU-MTU-20040212 |
| └ 83.237.80.0/24 | 256 | Customers_P2P_2025_00_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.81.0/24 | 256 | Customers_P2P_2025_01_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.82.0/24 | 256 | Customers_P2P_2025_02_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.83.0/24 | 256 | Customers_P2P_2025_03_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.84.0/24 | 256 | Customers_P2P_2025_04_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.85.0/24 | 256 | Customers_P2P_2025_05_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.86.0/24 | 256 | Customers_P2P_2025_06_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.87.0/24 | 256 | Customers_P2P_2025_07_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.88.0/24 | 256 | Customers_P2P_2025_08_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.89.0/24 | 256 | Customers_P2P_2025_09_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.90.0/24 | 256 | Customers_P2P_2025_10_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.91.0/24 | 256 | Customers_P2P_2025_11_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.92.0/24 | 256 | Customers_P2P_2025_12_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.93.0/24 | 256 | Customers_P2P_2025_13_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.94.0/24 | 256 | Customers_P2P_2025_14_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.95.0/24 | 256 | Customers_P2P_2025_15_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 13, 2025 | [email protected] via RU-MTU-20040212 |
| └ 83.237.96.0/24 | 256 | Customers_P2P_2025_16_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.97.0/24 | 256 | Customers_P2P_2025_17_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.98.0/24 | 256 | Customers_P2P_2025_18_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.99.0/24 | 256 | Customers_P2P_2025_19_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.100.0/24 | 256 | Customers_P2P_2025_20_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.101.0/24 | 256 | Customers_P2P_2025_21_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.102.0/24 | 256 | Customers_P2P_2025_22_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.103.0/24 | 256 | Customers_P2P_2025_23_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.104.0/24 | 256 | Customers_P2P_2025_24_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.105.0/24 | 256 | Customers_P2P_2025_25_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.106.0/24 | 256 | Customers_P2P_2025_26_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.107.0/24 | 256 | Customers_P2P_2025_27_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.108.0/24 | 256 | Customers_P2P_2025_28_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.109.0/24 | 256 | Customers_P2P_2025_29_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.110.0/24 | 256 | Customers_P2P_2025_30_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.111.0/24 | 256 | Customers_P2P_2025_31_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.112.0/24 | 256 | Customers_P2P_2025_32_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.113.0/24 | 256 | Customers_P2P_2025_33_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.114.0/24 | 256 | Customers_P2P_2025_34_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.115.0/24 | 256 | Customers_P2P_2025_35_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.116.0/24 | 256 | Customers_P2P_2025_36_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.117.0/24 | 256 | Customers_P2P_2025_37_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.118.0/24 | 256 | Customers_P2P_2025_38_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.119.0/24 | 256 | Customers_P2P_2025_39_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.120.0/24 | 256 | Customers_P2P_2025_40_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.121.0/24 | 256 | Customers_P2P_2025_41_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.122.0/24 | 256 | Customers_P2P_2025_42_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.123.0/24 | 256 | Customers_P2P_2025_43_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.124.0/24 | 256 | Customers_P2P_2025_44_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.125.0/24 | 256 | Customers_P2P_2025_45_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.126.0/24 | 256 | Customers_P2P_2025_46_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.127.0/24 | 256 | Customers_P2P_2025_47_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.128.0/24 | 256 | Customers_P2P_2025_48_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.129.0/24 | 256 | Customers_P2P_2025_49_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.130.0/24 | 256 | Customers_P2P_2025_50_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.131.0/24 | 256 | Customers_P2P_2025_51_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
| └ 83.237.132.0/24 | 256 | Customers_P2P_2025_52_WAN_NET | MTS PJSC | ASSIGNED PA | Jul 23, 2026 | [email protected] via RU-MTU-20040212 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
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 2005 · 21 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 83.237.0.0/16
- Netname
- RU-MTU-20040212
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Feb 12, 2004
- Updated
- May 24, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 12, 2004
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE