Data as of Nov 18, 2026

88.205.216.0/23

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

332 observations

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • 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 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.216.0 - 88.205.231.2554,096RU-RICH-YAMAL-2JSC Uralsvyazinform, a Yamalo-Nenetsk branchLIR-PARTITIONED PAAug 1, 2006abuse@rt.ru
via RU-RTK-200501212
└ 88.205.216.0/23512RU-RICH-YAMAL-NUR-5JSC Uralsvyazinform, a Yamalo-Nenetsk branchASSIGNED PADec 11, 2006abuse@rt.ru
via RU-RICH-YAMAL-2

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.216.0/21

Routing history

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

History

Handoffs
1