LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

5.10.7.0/24

3 residential-proxy exits · 30 days

Wemaconnect GmbH

Announcement
5.10.0.0/21
RPKI valid
Announced by
AS198726
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
14
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

68 observations

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • BottingTools
  • FlexyProxies
  • FloppyData
  • GonzoProxy
  • Infatica
  • NovaProxy
  • PacketStream
  • PrivateByte
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma

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.6.0 - 5.10.7.39296TMS-Radolfzell-1SW RadolfzellASSIGNED PAOct 19, 2015abuse@wemaconnect.de
via DE-WEMACONNECT-20120726
└ 5.10.7.40/298NET-IS-RdzIntegrated Systems, BoehringenASSIGNED PAOct 19, 2015abuse@wemaconnect.de
via DE-WEMACONNECT-20120726
└ 5.10.7.56/298NET-RDZ-Access-FischerunknownASSIGNED PANov 30, 2017abuse@wemaconnect.de
via DE-WEMACONNECT-20120726
└ 5.10.7.64 - 5.10.7.255192TMS-Radolfzell-2SW RadolfzellASSIGNED PANov 30, 2017abuse@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential24094%3
Business166.3%2

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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