Data as of Nov 17, 2026

217.68.56.0/21

10 residential-proxy exits · 30 days

Gemeente Den Haag

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
10
0.49% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
30
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

111 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • BottingTools
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • HideProxy
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • ThunderProxy
  • VProxy
  • VantageProxies

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.68.56.0/22
since Nov 2024
AS29263Business9Gemeente Den Haag
217.68.60.0/22
since Nov 2024
AS29263BusinessGemeente Den Haag

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.68.48.0/204,096NL-HAAGNET-20030707Gemeente Den Haag (ORG-GDH1-RIPE) · NLALLOCATED PAJul 7, 2003abuse@haagnet.net
└ 217.68.52.224 - 217.68.63.2552,848HAAGNETunknownASSIGNED PAFeb 5, 2026abuse@haagnet.net
via NL-HAAGNET-20030707

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 217.68.48.0/20

217.68.48.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1