Data as of Nov 14, 2026

82.180.64.0/18

185 residential-proxy exits · 30 days

WEMACOM Telekommunikation GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
185
1.1% of its addresses · 30 days
Always-on exits
3
1.6% of its exits
Spread
48 of 64
/24s with at least one exit
Providers
79
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

15K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LOKIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • 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
82.180.64.0/1816,384DE-WEMACOM-20031009WEMACOM Telekommunikation GmbH (ORG-WTG4-RIPE) · DEALLOCATED PANov 18, 2020abuse@wemacom.de
└ 82.180.64.0/204,096PPPoE-DYNAMIC-POOL-01unknownAGGREGATED-BY-LIRMay 30, 2025abuse@wemacom.de
via DE-WEMACOM-20031009
└ 82.180.80.0/204,096PPPoE-DYNAMIC-POOL-02unknownAGGREGATED-BY-LIRMay 30, 2025abuse@wemacom.de
via DE-WEMACOM-20031009
└ 82.180.96.0/204,096PPPoE-DYNAMIC-POOL-03unknownAGGREGATED-BY-LIRMay 30, 2025abuse@wemacom.de
via DE-WEMACOM-20031009
└ 82.180.112.0/204,096PPPoE-DYNAMIC-POOL-04unknownAGGREGATED-BY-LIRMay 30, 2025abuse@wemacom.de
via DE-WEMACOM-20031009

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
Apr 2021
Current origin since
Apr 2021 · 5.6 yr
Origin networks
1