Data as of Nov 18, 2026

188.17.147.64/28

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
25% of its addresses · listed by providers
Always-on exits
1
25% of its exits
Providers
31
selling exits here

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.16.0.0/14
since Oct 2018
AS12389Residential74,688
91 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.16.0.0/14262,144RU-RTK-20090203PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 3, 2009abuse@rt.ru
└ 188.17.147.64/2816AVIAENG-NETAviadvigatel JSC network, Perm, RussiaASSIGNED PADec 18, 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

188.17.144.0/20

Routing history

Pattern
Stable
First seen
Mar 2009
Current origin since
Aug 2017 · 9.2 yr
Origin networks
2
Last change of origin
Aug 2017
Recorded history

History

Handoffs
1