Data as of Nov 18, 2026

212.16.192.0/22

2 residential-proxy exits · 30 days

JSC RTComm.RU

Announcement
this exact prefix
No RPKI
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
8
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

5 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.16.193.0/2401
212.16.194.0/2401

Proxy providers listing exits

  • BottingTools
  • EZProxies
  • IPFly
  • IPPeak
  • NovaProxy
  • PuraRoute
  • RainProxy
  • RoamProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.16.192.0/20
since Nov 2007
AS8920Internet provider14JSC RTComm.RU
212.16.192.0/19
since May 2005
AS8920Internet provider18
1 always on
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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.16.192.0/198,192RU-RTCOMM-980806JSC RTComm.RU (ORG-RA25-RIPE) · RUALLOCATED PA—abuse@rtcomm.ru
└ 212.16.192.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.193.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.194.0/24256RTCJSC RTComm.RUASSIGNED PADec 20, 2001abuse@rtcomm.ru
via RU-RTCOMM-980806
└ 212.16.195.0/24256RTCJSC RTComm.RUASSIGNED PAJan 12, 2017abuse@rtcomm.ru
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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2016
Current origin since
Aug 2016 · 10 yr
Origin networks
1