Data as of Nov 12, 2026

37.44.40.0/23

4 residential-proxy exits · 30 days

OOO Smoltelecom

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
32
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

704 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
37.44.41.0/2412
37.44.40.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • LUMIPROXY
  • MangoProxy
  • NSocks
  • NiuProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.44.40.0/212,048RU-SMOLTELECOM-20120110OOO Smoltelecom (ORG-SL154-RIPE) · RUALLOCATED PAJan 10, 2012abuse@smoltelecom.ru
└ 37.44.40.0/23512SMOLTELECOM-CUSTOMER_30BITSSmoltelecom customers' /30 subnetsASSIGNED PADec 5, 2016abuse@smoltelecom.ru
via RU-SMOLTELECOM-20120110

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

Who has announced 37.44.40.0/21

37.44.40.0/21

Routing history

Pattern
Stable
First seen
Feb 2012
Current origin since
Feb 2012 · 15 yr
Origin networks
1