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

83.172.41.0/24

6 residential-proxy exits · 30 days

JSC Neotelecom · space held by JSC "ER-Telecom Holding"

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
27
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

931 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.172.0.0 - 83.172.59.25515,360RU-RAID-20040422JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PANov 29, 2018abuse@domru.ru
└ 83.172.40.0/221,024NEOTELECOM-NETNEOTELECOM, Internet service provider, Tomsk, RussiaASSIGNED PAFeb 13, 2007abuse@domru.ru
via RU-RAID-20040422

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 83.172.40.0/22

83.172.40.0/22

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jan 2008 · 19 yr
Origin networks
3
Last change of origin
Jan 2008
Recorded history

History

Handoffs
2