Data as of Nov 12, 2026

217.61.232.0/22

20 residential-proxy exits · 30 days

Ilm-Provider UG (haftungsbeschraenkt)

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

Residential-proxy exits

Proxy exits
20
2.0% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.2K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TalorData
  • Thordata
  • 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
217.61.232.0/221,024DE-ILMPROVIDER-20001101Ilm-Provider UG (haftungsbeschraenkt) (ORG-IU12-RIPE) · DEALLOCATED PAMay 12, 2016abuse@ilm-provider.de
└ 217.61.232.0/23512ILM-Provider-NET7unknownASSIGNED PAJul 11, 2017abuse@ilm-provider.de
via DE-ILMPROVIDER-20001101
└ 217.61.234.0/23512ILM-PROVIDER-NET8unknownASSIGNED PAFeb 1, 2018abuse@ilm-provider.de
via DE-ILMPROVIDER-20001101

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