Data as of Nov 13, 2026

2.57.116.0/24

28 residential-proxy exits · 30 days

wilhelm.tel GmbH

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

Residential-proxy exits

Proxy exits
28
11% of its addresses · 30 days
Providers
46
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

876 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.57.116.0/221,024DE-NORDERSTEDT-20190319wilhelm.tel GmbH (ORG-WN1-RIPE) · DEALLOCATED PASep 20, 2022abuse@wilhelm-tel.de
└ 2.57.116.0/23512WT-PPPOE-PRIVATE-CUSTOMER-NETunknownASSIGNED PAJul 10, 2025abuse@wilhelm-tel.de
via DE-NORDERSTEDT-20190319

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 2.57.116.0/22

2.57.116.0/22

Routing history

Pattern
Rotating
First seen
Apr 2019
Current origin since
Sep 2022 · 4.1 yr
Origin networks
7
Last change of origin
Sep 2022
Recorded history

History

Handoffs
8