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

185.23.32.0/23

8 residential-proxy exits · 30 days

JSC Telephone Company 'Sotcom'

Announcement
this exact prefix
No RPKI
Announced by
AS34467
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
1.6% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
22
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

210 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.23.32.0/2407
185.23.33.0/2401

Proxy providers listing exits

  • B2Proxy
  • BlurPath
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Evomi
  • Geonode
  • GhostConnect
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • NextProxy
  • NovaProxy
  • PrivateByte
  • ProxiesVision
  • Proxmint
  • Proxy4U
  • ProxyGeo
  • PuraRoute

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
185.23.32.0/23512RU-SOTCOM-20130405JSC Telephone Company "Sotcom" (ORG-JTC5-RIPE) · RUALLOCATED PAJun 3, 2025support@sotcom.ru
└ 185.23.32.0/24256NET_Ryazan-city_part_1unknownASSIGNED PAJun 3, 2025support@sotcom.ru
via RU-SOTCOM-20130405
└ 185.23.33.0/24256NET_Ryazan-city_part_2unknownASSIGNED PAJun 3, 2025support@sotcom.ru
via RU-SOTCOM-20130405

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2025
Current origin since
May 2025 · 1.5 yr
Origin networks
1