Data as of Nov 6, 2026
212.16.192.0/19
20 residential-proxy exits · 30 daysJSC RTComm.RU
Residential-proxy exits
Proxy exits
20
0.24% of its addresses · 30 days
Always-on exits
1
5.0% of its exits
Spread
9 of 32
/24s with at least one exit
Providers
50
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
1.6K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.16.222.0/24 | 1 | 1 | |
| 212.16.196.0/24 | 0 | 7 | |
| 212.16.203.0/24 | 0 | 6 | |
| 212.16.193.0/24 | 0 | 1 | |
| 212.16.194.0/24 | 0 | 1 | |
| 212.16.200.0/24 | 0 | 1 | |
| 212.16.207.0/24 | 0 | 1 | |
| 212.16.219.0/24 | 0 | 1 | |
| 212.16.221.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EZProxies
- EnigmaProxy
- FastProxy
- FlashProxy
- GSocks
- Geonix
- GloryCloud
- GonzoProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- LemonBright
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- PrivateByte
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- ProxyWing
- Proxyma
- PuraRoute
- RainProxy
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- Thordata
- VantageProxies
- VitalExclusive
- VitalProxy
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 |
|---|---|---|---|---|---|
| 212.16.192.0/20 since Nov 2007 | AS8920 | Internet provider | 17 | JSC RTComm.RU | |
| 212.16.192.0/22 since Aug 2016 | AS8920 | Internet provider | 2 | JSC RTComm.RU | |
| 212.16.197.0/24 since Aug 2016 | AS8920 | Internet provider | JSC RTComm.RU | ||
| 212.16.198.0/23 since Aug 2016 | AS8920 | Internet provider | JSC RTComm.RU | ||
| 212.16.198.0/24 since Sep 2022 | AS8920 | Internet provider | JSC RTComm.RU | ||
| 212.16.200.0/21 since Aug 2016 | AS8920 | Internet provider | 8 | JSC RTComm.RU | |
| 212.16.203.0/24 since May 2005 | AS8920 | Internet provider | 6 | JSC RTComm.RU | |
| 212.16.208.0/20 since Nov 2007 | AS8920 | Internet provider | 3 1 always on | JSC RTComm.RU | |
| 212.16.220.0/24 since May 2018 | AS8920 | Internet provider | JSC RTComm.RU |
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.16.192.0/19 | 8,192 | RU-RTCOMM-980806 | JSC RTComm.RU (ORG-RA25-RIPE) · RU | ALLOCATED PA | — | abuse@ |
| └ 212.16.192.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.193.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.194.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.195.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.198.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Jan 12, 2017 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.199.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | May 11, 2008 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.202.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.203.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Sep 28, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.204.0/24 | 256 | RTC | JSC Vostoktelecom | ASSIGNED PA | Jun 10, 2002 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.205.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Oct 17, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.207.0/24 | 256 | RTC | JSC Vostoktelecom | ASSIGNED PA | Jul 11, 2005 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.210.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Oct 14, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.211.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.212.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Dec 20, 2001 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.214.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Oct 14, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.215.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Jul 13, 2005 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.217.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Jul 13, 2005 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.218.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Sep 30, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.219.0/24 | 256 | RTC | JSC RTComm.ru | ASSIGNED PA | Aug 3, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.220.0/24 | 256 | RTC | JSC RTComm.RU | ASSIGNED PA | Oct 17, 2003 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.221.0/24 | 256 | RTC | CJSC RTComm.RU | ASSIGNED PA | Jul 5, 2007 | abuse@ via RU-RTCOMM-980806 |
| └ 212.16.222.0/24 | 256 | RTC | CJSC RTComm.RU | ASSIGNED PA | Jul 5, 2007 | abuse@ via RU-RTCOMM-980806 |
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
AS8920
RU
- Name
- JSC RTComm.RU
- Type
- Internet provider
- Registered
- Aug 7, 1998
- Domain
- rtcomm.ru
- Industry
- Hosting and Cloud Provider
- 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
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8920 | RIPE | Far Eastern Branch JSC RTComm.RU | AS8920-MNT | Sep 24, 2024 |
Whois
Registration for this announcement
- Range
- 212.
16. 192. 0/ 19 - Netname
- RU-RTCOMM-980806
- Registrant
- JSC RTComm.RU
- Registrant country
- RU
- Organization
- JSC RTComm.RU (ORG-RA25-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Not stated by the registry
- Updated
- Nov 13, 2020
- Maintainer
- AS8342-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Aug 6, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rtcomm. ru - Name
- RTComm.RU abuse
- Handle
- RTC-RU