Data as of Nov 14, 2026
213.87.0.0/16
1,058 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
1,058
1.6% of its addresses · 30 days
Always-on exits
162
15% of its exits
Spread
25 of 256
/24s with at least one exit
Providers
122
selling exits here
Oct 15, 2026 – Nov 13, 2026
Exits seen per day
609K observations
- Residential
- Mobile
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 213.87.196.0/24 | 100 | 255 | |
| 213.87.246.0/24 | 31 | 127 | |
| 213.87.195.0/24 | 29 | 256 | |
| 213.87.96.0/24 | 1 | 4 | |
| 213.87.104.0/24 | 1 | 3 | |
| 213.87.102.0/24 | 0 | 198 | |
| 213.87.194.0/24 | 0 | 173 | |
| 213.87.197.0/24 | 0 | 9 | |
| 213.87.103.0/24 | 0 | 7 | |
| 213.87.101.0/24 | 0 | 5 | |
| 213.87.84.0/24 | 0 | 3 | |
| 213.87.106.0/24 | 0 | 3 | |
| 213.87.198.0/24 | 0 | 2 | |
| 213.87.85.0/24 | 0 | 1 | |
| 213.87.87.0/24 | 0 | 1 | |
| 213.87.80.0/24 | 0 | 1 | |
| 213.87.13.0/24 | 0 | 1 | |
| 213.87.115.0/24 | 0 | 1 | |
| 213.87.72.0/24 | 0 | 1 | |
| 213.87.71.0/24 | 0 | 1 | |
| 213.87.45.0/24 | 0 | 1 | |
| 213.87.35.0/24 | 0 | 1 | |
| 213.87.100.0/24 | 0 | 1 | |
| 213.87.202.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CROXY
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HELODATA
- HPROXY
- HideProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPROCKET_BASIC
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYFALL
- PROXYLANE
- PROXYON
- PROXYSAVER
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 213.87.0.0/21 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.16.0/21 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.24.0/21 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.32.0/23 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.36.0/22 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.42.0/23 since Mar 2013 | AS15640 | Residential | MTS PJSC | ||
| 213.87.44.0/22 since May 2005 | AS13174 | Residential | 1 | MTS PJSC | |
| 213.87.48.0/22 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.50.0/23 since Feb 2025 | AS13174 | Residential | MTS PJSC | ||
| 213.87.52.0/24 since Dec 2024 | AS13174 | Residential | MTS PJSC | ||
| 213.87.64.0/22 since Mar 2014 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.70.0/23 since Mar 2014 | AS8359 | Mobile | 1 | MTS PJSC | |
| 213.87.72.0/22 since Oct 2005 | AS35473 | Mobile | 1 | MTS PJSC | |
| 213.87.76.0/23 since Aug 2013 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.80.0/20 since Apr 2013 | AS8359 | Mobile | 6 | MTS PJSC | |
| 213.87.80.0/22 since Apr 2026 | AS8359 | Mobile | 1 | MTS PJSC | |
| 213.87.94.0/23 since Apr 2026 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.96.0/24 since Aug 2016 | AS39811 | Residential | 4 1 always on | MTS PJSC | |
| 213.87.97.0/24 since May 2008 | AS39811 | Residential | MTS PJSC | ||
| 213.87.98.0/23 since May 2024 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.100.0/24 since Oct 2023 | AS8359 | Mobile | 1 | MTS PJSC | |
| 213.87.101.0/24 since Apr 2026 | AS8359 | Mobile | 5 | MTS PJSC | |
| 213.87.102.0/24 since Aug 2016 | AS39811 | Residential | 198 | MTS PJSC | |
| 213.87.103.0/24 since Aug 2016 | AS39811 | Residential | 7 | MTS PJSC | |
| 213.87.104.0/24 since Dec 2023 | AS8359 | Mobile | 3 1 always on | MTS PJSC | |
| 213.87.105.0/24 since Oct 2023 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.106.0/23 since Dec 2023 | AS8359 | Mobile | 3 | MTS PJSC | |
| 213.87.116.0/23 since Sep 2010 | AS28884 | Mobile | MTS PJSC | ||
| 213.87.124.0/23 since May 2012 | AS28884 | Mobile | MTS PJSC | ||
| 213.87.128.0/19 since Sep 2015 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.160.0/22 since Sep 2015 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.192.0/21 since Apr 2026 | AS8359 | Mobile | 695 129 always on | MTS PJSC | |
| 213.87.200.0/22 since Dec 2015 | AS8359 | Mobile | 1 | MTS PJSC | |
| 213.87.208.0/23 since May 2014 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.210.0/23 since May 2024 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.240.0/22 since Aug 2013 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.244.0/23 since Aug 2013 | AS8359 | Mobile | MTS PJSC | ||
| 213.87.246.0/24 since Dec 2023 | AS8359 | Mobile | 127 31 always on | MTS PJSC | |
| 213.87.248.0/22 since Aug 2013 | AS8359 | Mobile | MTS PJSC |
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 |
|---|---|---|---|---|---|---|
| 213.87.0.0/16 | 65,536 | RU-MTU-20000410 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Dec 14, 2001 | abuse@ |
| └ 213. | 10,240 | MTSNET | Mobile TeleSystems OJSC | ASSIGNED PA | — | abuse@ via RU-MTU-20000410 |
| └ 213.87.40.0/23 | 512 | MTSGPRS | Mobile TeleSystems, OJSC, GPRS/3G/LTE Gn infrastructure in Moscow | ASSIGNED PA | — | abuse@ via RU-MTU-20000410 |
| └ 213.87.42.0/23 | 512 | MTS-PERM | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jul 1, 2019 | abuse@ |
| └ 213. | 3,072 | MTSNET2 | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Mar 5, 2020 | abuse@ |
| └ 213.87.56.0/21 | 2,048 | MTSNET3 | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Mar 5, 2020 | abuse@ |
| └ 213.87.64.0/23 | 512 | MTSNET4 | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Mar 5, 2020 | abuse@ |
| └ 213.87.66.0/24 | 256 | SINGER-COMPUTER-NET | Mobile TeleSystems, OJSC | ASSIGNED PA | Apr 2, 2004 | abuse@ via RU-MTU-20000410 |
| └ 213.87.67.0/24 | 256 | MTSNET-NN | MTSNET infra in N.Novgorod | ASSIGNED PA | Oct 22, 2009 | abuse@ via RU-MTU-20000410 |
| └ 213.87.68.0/23 | 512 | GPRS-INFRA | Mobile TeleSystems, OJSC, GPRS/3G/LTE Gn infrastructure in Moscow | ASSIGNED PA | Jun 16, 2004 | abuse@ via RU-MTU-20000410 |
| └ 213.87.70.0/23 | 512 | MTSNET3 | MTSNET infrastructure in N.Novgorod | ASSIGNED PA | Jun 16, 2005 | abuse@ via RU-MTU-20000410 |
| └ 213. | 784 | MTSNET-URAL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213.87.75.16/28 | 16 | MTSNET-URAL-MAIL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213.87.75.32/28 | 16 | MTSNET-URAL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213.87.75.48/29 | 8 | MTSNET-URAL-MAIL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213. | 104 | MTSNET-URAL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213.87.75.160/28 | 16 | MTSNET-URAL-MAIL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213. | 80 | MTSNET-URAL | MTS PJSC (ORG-ZM1-RIPE) · RU | ASSIGNED PA | Jun 5, 2019 | abuse@ |
| └ 213.87.76.0/23 | 512 | MTSNET-URAL-2 | Ekaterinburg (Ural) division of Mobile Telesystems OJSC | ASSIGNED PA | Sep 6, 2006 | abuse@ via RU-MTU-20000410 |
| └ 213.87.78.0/23 | 512 | Gn-INFRA | Mobile TeleSystems, OJSC, GPRS/3G/LTE Gn infrastructure in Moscow | ASSIGNED PA | Mar 2, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.80.0/20 | 4,096 | MTSGPRS-2 | Mobile subscribers pool | ASSIGNED PA | Jan 19, 2005 | abuse@ via RU-MTU-20000410 |
| └ 213.87.96.0/23 | 512 | MTSNET-VLD | Vladivostok (Far East) division of Mobile Telesystems OJSC | ASSIGNED PA | Apr 4, 2006 | abuse@ via RU-MTU-20000410 |
| └ 213.87.98.0/23 | 512 | MTSNET-VLD | Vladivostok (Far East) division of Mobile Telesystems OJSC | ASSIGNED PA | Apr 4, 2006 | abuse@ via RU-MTU-20000410 |
| └ 213.87.100.0/22 | 1,024 | MTSNET-DV-B | MTSNET Broadband infra in MR DV | ASSIGNED PA | Jun 1, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.104.0/23 | 512 | MTSNET-VLD104 | Vladivostok division of Mobile Telesystems OJSC | ASSIGNED PA | Aug 1, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.106.0/23 | 512 | MTSNET-VLD106 | Vladivostok division of Mobile Telesystems OJSC | ASSIGNED PA | Sep 6, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.108.0/23 | 512 | MTSNET-VLD108 | Vladivostok division of Mobile Telesystems OJSC | ASSIGNED PA | Sep 6, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.110.0/23 | 512 | MTSNET-VLD110 | Vladivostok division of Mobile Telesystems OJSC | ASSIGNED PA | Sep 6, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.112.0/23 | 512 | MTSNET-SIB | Mobile subscribers pool | ASSIGNED PA | Oct 28, 2009 | abuse@ via RU-MTU-20000410 |
| └ 213.87.114.0/23 | 512 | MTSNET-SIB1 | Mobile subscribers pool | ASSIGNED PA | Mar 19, 2010 | abuse@ via RU-MTU-20000410 |
| └ 213.87.116.0/23 | 512 | MTSNET-SIB2 | MTSNET infra in Siberia | ASSIGNED PA | Mar 19, 2010 | abuse@ via RU-MTU-20000410 |
| └ 213.87.118.0/23 | 512 | MTSNET-SIB3 | Mobile subscribers pool | ASSIGNED PA | Oct 18, 2010 | abuse@ via RU-MTU-20000410 |
| └ 213.87.120.0/23 | 512 | MTSNET-SIB4 | Mobile subscribers pool | ASSIGNED PA | Mar 9, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.122.0/23 | 512 | MTSNET-SIB5 | MTSNET GPRS/3G infra in Siberia | ASSIGNED PA | Apr 19, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.124.0/23 | 512 | MTSNET-SIB6 | MR-SIB-MTS infra in Siberia, Norilsk | ASSIGNED PA | Jan 18, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.126.0/23 | 512 | MTSGPRS | Mobile subscribers pool | ASSIGNED PA | Jun 5, 2015 | abuse@ via RU-MTU-20000410 |
| └ 213.87.128.0/19 | 8,192 | MTSGPRS-3 | Mobile subscribers pool | ASSIGNED PA | Aug 25, 2015 | abuse@ via RU-MTU-20000410 |
| └ 213.87.160.0/22 | 1,024 | MTSGPRS-4 | Mobile subscribers pool | ASSIGNED PA | Sep 16, 2015 | abuse@ via RU-MTU-20000410 |
| └ 213.87.192.0/21 | 2,048 | MTSNET-Ufa | MTSNET infra in Ufa | ASSIGNED PA | Feb 3, 2010 | abuse@ via RU-MTU-20000410 |
| └ 213.87.200.0/21 | 2,048 | MTSNET-MSK | MTS IT infrastructure | ASSIGNED PA | Apr 13, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.208.0/23 | 512 | MTSNET-SPB | MTSNET SPB infra | ASSIGNED PA | Jun 8, 2012 | abuse@ via RU-MTU-20000410 |
| └ 213.87.224.0/23 | 512 | MTSGPRS-6 | Mobile subscribers pool | ASSIGNED PA | Jun 5, 2015 | abuse@ via RU-MTU-20000410 |
| └ 213.87.240.0/22 | 1,024 | MTSGPRS-5 | Mobile subscribers pool | ASSIGNED PA | Oct 24, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.244.0/23 | 512 | MTSNET-URAL-APN-Static-IP | MTSNET gprs-infra in Ural | ASSIGNED PA | Nov 24, 2011 | abuse@ via RU-MTU-20000410 |
| └ 213.87.248.0/22 | 1,024 | MTSNET-URAL-NAT | MTSNET gprs-infra in Ural | ASSIGNED PA | Dec 25, 2012 | abuse@ via RU-MTU-20000410 |
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
65,536 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Mobile | 54,016 | 82% | 39 | |
| Residential | 11,520 | 18% | 14 |
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
- Jun 2016
- Current origin since
- Jun 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 213.87.0.0/16 | AS8359 | /16 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8359 | RIPE | MTS PJSC | MTU-NOC MTSNET-MNT | Aug 5, 2015 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 213.87.0.0/19 | AS13174 | RIPE | Mobile TeleSystems OJSC | MTSNET-MNT | Jul 15, 2003 |
| 213.87.32.0/21 | AS13174 | RIPE | Mobile TeleSystems OJSC | MTSNET-MNT | Apr 22, 2003 |
| 213.87.48.0/21 | AS13174 | RIPE | Mobile TeleSystems OJSC | MTSNET-MNT | Nov 20, 2009 |
| 213.87.56.0/22 | AS38996 | RIPE | Mobile TeleSystems OJSC | MTSNET-MNT | Oct 7, 2010 |
| 213.87.60.0/22 | AS38996 | RIPE | Mobile TeleSystems OJSC | MTSNET-MNT | Oct 7, 2010 |
| 213.87.96.0/23 | AS8359 | RIPE | Vladivostok (Far East) division of Mobile Telesystems PJSC | MTU-NOC | Jun 17, 2020 |
| 213.87.96.0/23 | AS39811 | RIPE | Vladivostok (Far East) division of Mobile Telesystems OJSC | MR-DV-MTS-MNT | May 15, 2008 |
| 213.87.100.0/22 | AS8359 | RIPE | MR DV division of Mobile Telesystems PJSC | MTU-NOC | Nov 28, 2025 |
| 213.87.100.0/22 | AS39811 | RIPE | MR DV division of Mobile Telesystems OJSC | MR-DV-MTS-MNT | Jun 1, 2011 |
| 213.87.104.0/23 | AS8359 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | Jun 16, 2020 |
| 213.87.104.0/23 | AS39811 | RIPE | Vladivostok division of Mobile Telesystems OJSC | MR-DV-MTS-MNT | Aug 1, 2012 |
| 213.87.108.0/23 | AS8359 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | Jun 16, 2020 |
| 213.87.108.0/23 | AS39811 | RIPE | Vladivostok division of Mobile Telesystems OJSC | MR-DV-MTS-MNT | Sep 6, 2012 |
| 213.87.110.0/23 | AS8359 | RIPE | Vladivostok division of Mobile Telesystems PJSC | MTU-NOC | Jun 16, 2020 |
| 213.87.110.0/23 | AS39811 | RIPE | Vladivostok division of Mobile Telesystems OJSC | MR-DV-MTS-MNT | Sep 6, 2012 |
| 213.87.112.0/23 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.112.0/24 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.113.0/24 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.114.0/23 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.114.0/24 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.115.0/24 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.118.0/23 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.120.0/23 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.122.0/23 | AS28884 | RIPE | MTS PJSC, MR Sibir | MR-SIB-MTS-MNT | Oct 9, 2015 |
| 213.87.126.0/23 | AS28884 | RIPE | MTS OJSC | MTU-NOC | Jun 5, 2015 |
| 213.87.200.0/21 | AS8359 | RIPE | Mobile TeleSystems, OJSC | MTU-NOC | Oct 3, 2013 |
| 213.87.204.0/22 | AS8359 | RIPE | Mobile TeleSystems, PJSC | MTSNET-MNT MTU-NOC | Mar 4, 2016 |
| 213.87.224.0/23 | AS28884 | RIPE | MTS OJSC | MTU-NOC | Jun 5, 2015 |
Whois
Registration for this announcement
- Range
- 213.
87. 0. 0/ 16 - Netname
- RU-MTU-20000410
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 14, 2001
- Updated
- Sep 29, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Apr 10, 2000
- Status
- assigned
Report abuse
Abuse contact
- abuse@
mtu. ru - Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE