Data as of Nov 13, 2026

5.10.4.0/26

2 residential-proxy exits · 30 days

Wemaconnect GmbH

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
2
3.1% of its addresses · 30 days
Always-on exits
3
100% of its exits
Providers
49
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

369 observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • KocerRoxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.10.0.0/212,048DE-WEMACONNECT-20120726Wemaconnect GmbH (ORG-WG184-RIPE) · DEALLOCATED PADec 3, 2025abuse@wemaconnect.de
└ 5.10.4.0/2664TMS-Woerth-2EZV GmbH & Co. KGASSIGNED PAJun 4, 2014abuse@wemaconnect.de
via DE-WEMACONNECT-20120726

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 5.10.0.0/21

5.10.0.0/21

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Jul 2018 · 8.3 yr
Origin networks
1