Data as of Nov 13, 2026

196.3.164.0/22

23 residential-proxy exits · 30 days

Vox Telecom Ltd

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

Residential-proxy exits

Proxy exits
23
2.2% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
38
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CROXY
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GhostConnect
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE
  • 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
196.3.164.0/221,024Vox-TelecomVox Telecom Ltd (ORG-DPBO1-AFRINIC) · ZAALLOCATED PA—abuse@voxtelecom.co.za
└ 196.3.164.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.165.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.166.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.167.0/2732Vox-TelecomJHB Customer Hosted VLANASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.167.32/2732Vox-TelecomBTG Net VLAN 167ASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.167.64/2664Vox-TelecomJHB Customer System VLANASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.167.128/2664Vox-TelecomBGT AdminASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom

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
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1