Data as of Nov 16, 2026

216.40.79.0/24

7 residential-proxy exits · 30 days

GTHost · space held by inetCloud

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
30
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

757 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BottingTools
  • CliProxy
  • DataImpulse
  • EZProxies
  • FastProxy
  • FlashProxy
  • Geonode
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • Novada
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • YumiProxy
  • ZENPROXY_LITE

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
216.40.76.0/221,024INETWSinetCloud (INETC-5) · CADirect AllocationDec 26, 2024av@inet.ws
└ 216.40.79.0/24256INETWS-PARISinetCloud (C11528662) · CAReassignedFeb 28, 2026av@inet.ws
via INETWS

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
Jun 2007
Current origin since
Feb 2026 · 9 mo
Origin networks
2
Last change of origin
Feb 2026
Recorded history

History

Handoffs
1