Data as of Nov 17, 2026

185.174.16.0/22

28 residential-proxy exits · 30 days

ZNET Telekom Zrt

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

Residential-proxy exits

Proxy exits
28
2.7% of its addresses · 30 days
Always-on exits
1
3.6% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
49
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.8K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • 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
185.174.16.0/221,024HU-ZNETTELEKOM-20161020ZNET Telekom Zrt (ORG-ZTZ1-RIPE) · HUALLOCATED PANov 19, 2018abuse@zt.hu
└ 185.174.16.0/24256HU-ZNETTELEKOMZNET Telekom Zrt.ASSIGNED PAOct 20, 2016abuse@zt.hu
via HU-ZNETTELEKOM-20161020
└ 185.174.17.0/24256HU-ZNETTELEKOM-20181203ZNET Telekom ZrtASSIGNED PAOct 20, 2016abuse@zt.hu
via HU-ZNETTELEKOM-20161020
└ 185.174.18.0/24256HU-ZNETTELEKOM-20181203ZNET Telekom ZrtASSIGNED PAOct 20, 2016abuse@zt.hu
via HU-ZNETTELEKOM-20161020
└ 185.174.19.0/24256HU-ZNETTELEKOM-20181203ZNET Telekom ZrtASSIGNED PAOct 20, 2016abuse@zt.hu
via HU-ZNETTELEKOM-20161020

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
Oct 2016
Current origin since
Oct 2016 · 10 yr
Origin networks
1