Data as of Nov 16, 2026

76.164.203.0/24

50 residential-proxy exits · 30 days

Interkvm Host SRL

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

Residential-proxy exits

Proxy exits
50
20% of its addresses · 30 days
Always-on exits
1
2.0% of its exits
Providers
45
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive

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
76.164.200.0/221,024RO-INTERKVM1-20060927Interkvm Host SRL (ORG-IHS20-RIPE) · ROALLOCATED PAOct 1, 2024report@zetservers.com
└ 76.164.203.0/24256ZetServers-MadridunknownLIR-PARTITIONED PADec 4, 2024report@zetservers.com
via RO-INTERKVM1-20060927

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
Reactivated
First seen
Apr 2021
Current origin since
Feb 2025 · 1.8 yr
Origin networks
2
Last change of origin
Feb 2025
Recorded history

History

Handoffs
1