Data as of Nov 20, 2026

188.16.152.0/21

5 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
5
0.24% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
28
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

541 observations

Proxy providers listing exits

  • 9HTTP
  • Ake.net
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.16.144.0/20
since Mar 2017
AS12389Residential581PJSC Rostelecom
188.16.0.0/14
since Oct 2018
AS12389Residential74,688
99 always on
PJSC Rostelecom

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
188.16.0.0/14262,144RU-RTK-20090203PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 3, 2009abuse@rt.ru
└ 188.16.152.0/212,048USI_ADSL_USERSDynamic distribution IP's for broadband servicesASSIGNED PASep 17, 2009abuse@rt.ru
via RU-RTK-20090203

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
Apr 2009
Current origin since
Apr 2017 · 9.6 yr
Origin networks
2
Last change of origin
Apr 2017
Recorded history

History

Handoffs
1