Data as of Nov 13, 2026

37.32.48.0/21

19 residential-proxy exits · 30 days

Enivest AS

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

Residential-proxy exits

Proxy exits
19
0.93% of its addresses · 30 days
Always-on exits
4
21% of its exits
Spread
6 of 8
/24s with at least one exit
Providers
40
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

7.6K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • Webshare

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
37.32.48.0/212,048NO-ENIVEST-20120102Enivest AS (ORG-EA55-RIPE) · NOALLOCATED PAJan 2, 2012abuse@enivest.no
└ 37.32.48.0/23512Enivest-FTH-AGRunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102
└ 37.32.50.0/24256Enivest-FTH-AGRunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102
└ 37.32.51.0/24256Enivest-FTH-HardbakkeunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102
└ 37.32.52.0/24256Enivest-FTH-VassendenunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102
└ 37.32.53.0/24256Enivest-FTHunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102
└ 37.32.54.0/23512Enivest-FTHunknownASSIGNED PAJun 18, 2018abuse@enivest.no
via NO-ENIVEST-20120102

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 this prefix

Summary

Routing history

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