Data as of Nov 11, 2026

37.138.158.0/24

45 residential-proxy exits · 30 days

EWE TEL GmbH

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

Residential-proxy exits

Proxy exits
45
18% of its addresses · 30 days
Providers
45
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

789 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.138.0.0/1665,536DE-EWETEL-20120223EWE TEL GmbH (ORG-ETG2-RIPE) · DEALLOCATED PAFeb 23, 2012abuse@ewetel.de
└ 37.138.122.0 - 37.138.162.25510,496EWETEL-DYNDSL-BKP4unknownASSIGNED PAMar 5, 2012abuse@ewetel.de
via DE-EWETEL-20120223

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 37.138.0.0/16

37.138.0.0/16

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1