Data as of Nov 11, 2026

212.3.32.0/24

4 residential-proxy exits · 30 days

Jetnet Wimax S.A

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
39
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • PacketStream
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.3.32.0/22
since Aug 2017
AS39155Residential7
1 always on
Jetnet Wimax S.A
212.3.32.0/19
since Aug 2017
AS39155Residential51
6 always on
Jetnet Wimax S.A

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
212.3.32.0/198,192ES-JETNET-20090109Jetnet Wimax S.A (ORG-CCS3-RIPE) · ESALLOCATED PAJan 9, 2009soporte@jetnet.es
└ 212.3.32.0/212,048JETNETjetnet.esASSIGNED PAApr 8, 2009soporte@jetnet.es
via ES-JETNET-20090109

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

Summary

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Aug 2024 · 2.2 yr
Origin networks
1