Data as of Nov 10, 2026

37.134.166.0/24

5 residential-proxy exits · 30 days

Orange Espagne SA

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
35
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

3.2K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.134.0.0/16
since Jun 2018
AS12479Mobile2,435
215 always on
Orange Espagne SA

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.132.0.0/14262,144ES-JAZZTEL-20120221Orange Espagne SA (ORG-JTS1-RIPE) · ESALLOCATED PAFeb 21, 2012abuse.es@masorange.es
└ 37.134.0.0/1665,536JAZZTEL-MOBILEJazztel mobile servicesASSIGNED PAFeb 22, 2012abuse.es@masorange.es
via ES-JAZZTEL-20120221

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

Covering aggregate above, the prefix's own history below

37.134.164.0/22

Routing history

Pattern
Stable
First seen
Feb 2018
Current origin since
Jul 2020 · 6.3 yr
Origin networks
1