Data as of Nov 20, 2026

195.161.96.0/20

3 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
3
0.07% of its addresses · 30 days
Spread
3 of 16
/24s with at least one exit
Providers
16
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

56 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
195.161.98.0/2401
195.161.103.0/2401
195.161.104.0/2401

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • HideProxy
  • IPFly
  • NextProxy
  • NovaProxy
  • ProxiesVision
  • ProxyGeo
  • PuraRoute
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.161.0.0/16
since May 2005
AS8342Internet provider76JSC 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
195.161.0.0/1665,536RU-RTCOMM-970605JSC RTComm.RU (ORG-RA25-RIPE) · RUALLOCATED PAJan 9, 2002abuse@rtcomm.ru
└ 195.161.107.0/24256RT-CLNT-AMTSPB"AMT Group" RussiaASSIGNED PA—abuse@rtcomm.ru
via RU-RTCOMM-970605

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
Mar 2021
Current origin since
Mar 2021 · 5.7 yr
Origin networks
1