Data as of Nov 20, 2026

213.162.196.0/24

2 residential-proxy exits · 30 days

FALBOX S.L. trading as NIXVAL

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
11
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

7.3K observations

Proxy providers listing exits

  • DataImpulse
  • EVOPROXY
  • GoProxies
  • IPFly
  • PROXYCOVE
  • Proxmint
  • Proxy4U
  • ProxyRack
  • Proxying
  • Q2IP
  • RH7Proxy

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
213.162.192.0/198,192ES-NIXVAL-20000418FALBOX S.L. trading as NIXVAL (ORG-AS7-RIPE) · ESALLOCATED PA—abuse@nixval.com
└ 213.162.196.0/2732NIXVAL_CUST_196unknownASSIGNED PAOct 24, 2012abuse@nixval.com
via ES-NIXVAL-20000418
└ 213.162.196.64/2664Cust_NixvalunknownASSIGNED PAMar 13, 2017abuse@nixval.com
via ES-NIXVAL-20000418
└ 213.162.196.128/2664Cust_Polartel1unknownASSIGNED PAMar 13, 2017abuse@nixval.com
via ES-NIXVAL-20000418
└ 213.162.196.192/2664Cust_Polartel2unknownASSIGNED PAMar 13, 2017abuse@nixval.com
via ES-NIXVAL-20000418

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 2026
Current origin since
Jan 2026 · 10 mo
Origin networks
1