Data as of Nov 20, 2026

134.101.252.0/22

11 residential-proxy exits · 30 days

wilhelm.tel GmbH

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

Residential-proxy exits

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

Exits seen per day

1.4K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
134.101.128.0/1732,768DE-NORDERSTEDT-19890522wilhelm.tel GmbH (ORG-WN1-RIPE) · DEALLOCATED PAAug 16, 2017abuse@wilhelm-tel.de
└ 134.101.252.0/221,024CMTS-CABLE-MODEM-CUSTOMER-NETwilhelm.tel GmbHASSIGNED PAOct 12, 2017abuse@wilhelm-tel.de
via DE-NORDERSTEDT-19890522

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 134.101.128.0/17

134.101.128.0/17

Routing history

Pattern
Stable
First seen
May 2016
Current origin since
Oct 2017 · 9.1 yr
Origin networks
2
Last change of origin
Oct 2017
Recorded history

History

Handoffs
1