LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

217.23.131.0/24

3 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
this exact prefix
No RPKI
Announced by
AS25227
Type
Business
52% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
26
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

319 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
217.23.130.0/23512RU-RAID-20001005JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAOct 5, 2026abuse@domru.ru
└ 217.23.131.11/321CARAVAN-NOCunknownASSIGNED PAFeb 3, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.12/304CARAVAN-NOCunknownASSIGNED PAFeb 3, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.16/298CARAVAN-ADMINunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.24/298CARAVAN-ADMINunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.48/298CARAVAN-NOCunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.64/298CARAVAN-NOCunknownASSIGNED PAFeb 4, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.80/298CARAVAN-NOCunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.104/298CARAVAN-NOCunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.136/298CARAVAN-NOCunknownASSIGNED PAFeb 10, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.144/298CARAVAN-NOCunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.152/298LL13434unknownASSIGNED PASep 7, 2016abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.168/298DL1401unknownASSIGNED PAFeb 5, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.192/298CARAVAN-NOCunknownASSIGNED PAJan 27, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.208/2816CARAVAN-NOCunknownASSIGNED PASep 23, 2016abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.232/298CARAVAN-NOCunknownASSIGNED PAFeb 26, 2015abuse@domru.ru
via RU-RAID-20001005
└ 217.23.131.240/2816CARAVAN-NOCunknownASSIGNED PAJan 23, 2015abuse@domru.ru
via RU-RAID-20001005

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

256 addresses
TypeAddressesShareRanges
Business13352%16
Unknown12348%10

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2015
Current origin since
Mar 2019 · 7.6 yr
Origin networks
2
Last change of origin
Mar 2019
Recorded history

History

Handoffs
1