Data as of Nov 19, 2026

37.60.139.0/24

7 residential-proxy exits · 30 days

Neterra Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
3
43% of its exits
Providers
44
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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.60.138.0 - 37.60.141.2551,024BG-NETERRAIP-20120118Neterra Ltd. (ORG-NL38-RIPE) · BGALLOCATED PADec 10, 2021abuse@neterra.net
└ 37.60.139.0/24256NETERRA-HOMENET-SOFIAunknownASSIGNED PASep 25, 2012abuse@neterra.net
via BG-NETERRAIP-20120118

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
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1