Data as of Nov 10, 2026

88.205.232.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
27
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.2K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.205.128.0/17
since Jul 2017
AS12389Residential70
12 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
88.205.128.0/1732,768RU-RTK-200501212PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 12, 2005abuse@rt.ru
└ 88.205.232.0 - 88.205.255.2556,144RU-RICH-YAMAL-1OJSC Uralsvyazinform, a Yamalo-Nenetsk branchLIR-PARTITIONED PADec 22, 2005abuse@rt.ru
via RU-RTK-200501212
└ 88.205.232.0/24256RU-RICH-YAMAL-NOY-3JSC Rostelecom, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1

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

88.205.232.0/21

Routing history

Pattern
Stable
First seen
Feb 2006
Current origin since
Mar 2017 · 9.7 yr
Origin networks
2
Last change of origin
Mar 2017
Recorded history

History

Handoffs
1