Data as of Nov 21, 2026

212.16.207.0/24

1 residential-proxy exit · 30 days

JSC RTComm.RU

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

91 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • GEEKPROXY_FLEX
  • GSocks
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.16.192.0/20
since Nov 2007
AS8920Internet provider10JSC RTComm.RU
212.16.192.0/19
since May 2005
AS8920Internet provider14
1 always on
JSC RTComm.RU

Registrations in this block

The registry's network records over this block, widest first, each 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.207.0/24256RTCJSC VostoktelecomASSIGNED PAJul 11, 2005abuse@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

212.16.200.0/21

Routing history

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