Data as of Nov 21, 2026

164.160.36.0/22

17 residential-proxy exits · 30 days

Jacqco Management CC

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

Residential-proxy exits

Proxy exits
17
1.7% of its addresses · 30 days
Always-on exits
2
12% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
47
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

2.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
164.160.36.0/2419
164.160.38.0/2413
164.160.37.0/2405

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • AnyIP
  • BestProxy
  • BlurPath
  • BottingTools
  • Byteful
  • CROXY
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXORA
  • Proxies.fo
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • 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
164.160.36.0/221,024JACQCO-MANAGEMENTJacqco Management CC (ORG-JMC1-AFRINIC) · ZAALLOCATED PA——
└ 164.160.36.0/24256Gigazone_Internet_Broadband_164_160_36_0Addresses used to provide Broadband access to Gigazone Internet customerASSIGNED PA——
└ 164.160.37.0/24256Gigazone_Internet_Broadband_164_160_37_0Addresses used to provide Business CustomersASSIGNED PA——
└ 164.160.38.0/24256Gigazone_Internet_Broadband_Vumatel_KZN_164_160_38_0Assigned to Vumatel Clients KZNASSIGNED PA——
└ 164.160.39.0/24256Gigazone_Interet_Broadband_164_160_39_0Assigned to FTTH ClientsASSIGNED PA——

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2016
Current origin since
Jun 2016 · 10 yr
Origin networks
1