Data as of Nov 18, 2026

188.32.145.0/24

12 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
3
25% of its exits
Providers
44
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

12K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.32.0.0/1665,536RU-RTK-20110930PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 30, 2011abuse@rt.ru
└ 188.32.128.0/198,192NCN-BBCUSTNCNET Broadband customersASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20110930

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

Who has announced 188.32.0.0/16

188.32.0.0/16

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Oct 2011 · 15 yr
Origin networks
1