Data as of Nov 16, 2026

88.205.240.0/20

4 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
4
0.10% of its addresses · 30 days
Spread
2 of 16
/24s with at least one exit
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
88.205.240.0/2403
88.205.241.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LightningProxies
  • NSocks
  • NodeMaven
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • SpyderProxy
  • TrustProxy
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.205.128.0/17
since Jul 2017
AS12389Residential70
9 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
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.240.0/23512RU-RICH-YAMAL-MUR-1JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.242.0/23512RU-RICH-YAMAL-GUB-1JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.244.0/25128RU-RICH-YAMAL-TS-2JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.244.128/25128RU-RICH-YAMAL-TS-3JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.245.0/25128RU-RICH-YAMAL-KOR-1JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.245.128/2664RU-RICH-YAMAL-NOY-4JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.245.192/2664RU-RICH-YAMAL-NOY-5JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.246.0/24256RU-RICH-YAMAL-NUR-3JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.247.0/24256RU-RICH-YAMAL-NUR-2JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.248.0/23512RU-RICH-YAMAL-NUR-1JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PAOct 25, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.250.0/23512USI_ADSL_USERSDynamic distribution IP's for broadband servicesASSIGNED PAMar 20, 2012abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.252.0/23512RU-RICH-YAMAL-NAD-3JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.254.0/24256RU-RICH-YAMAL-NAD-2JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PASep 1, 2006abuse@rt.ru
via RU-RICH-YAMAL-1
└ 88.205.255.0/24256RU-RICH-YAMAL-NAD-1JSC Uralsvyazinform, 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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,58488%2
Business51213%5

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

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