Data as of Nov 11, 2026

196.3.176.0/22

26 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
26
2.5% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
59
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

760 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
196.3.179.0/24020
196.3.178.0/2406

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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.176.0/221,024Vox-TelecomVox Telecom Ltd (ORG-DPBO1-AFRINIC) · ZAALLOCATED PA—abuse@voxtelecom.co.za
└ 196.3.176.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.177.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.178.0/24256Vox-TelecomVox TelecomASSIGNED PA—abuse@voxtelecom.co.za
via Vox-Telecom
└ 196.3.179.0/24256Vox-TelecomVox TelecomASSIGNED 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