Data as of Nov 13, 2026

92.255.218.0/24

14 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

486 observations

Proxy providers listing exits

  • Ake.net
  • ByteProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • GSocks
  • IPFly
  • IPMUSK
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NiuProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • TORCHPROXIES_X
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.255.216.0/21
since Sep 2013
AS41727Residential171
3 always on
JSC "ER-Telecom Holding"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.255.128.0/1732,768RU-RAID-20071228JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PADec 28, 2007abuse@domru.ru
└ 92.255.216.0/212,048ERTH-KIROV-PPPOE-8-NETJSC "ER-Telecom Holding" Kirov Branch (ORG-CHKB3-RIPE) · RUASSIGNED PASep 6, 2013abuse@domru.ru
via RU-RAID-20071228

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

92.255.216.0/22

Routing history

Pattern
Stable
First seen
Jan 2008
Current origin since
Dec 2017 · 8.9 yr
Origin networks
3
Last change of origin
Jan 2014
Recorded history

History

Handoffs
2