Data as of Nov 16, 2026

185.15.136.0/24

8 residential-proxy exits · 30 days

m3connect GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
9
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

22 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • EnigmaProxy
  • FloppyData
  • NovaProxy
  • ProxyEmpire
  • Thordata
  • VantageProxies
  • 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
185.15.136.0/24256DE-M3CONNECT-20191224m3connect GmbH (ORG-MG248-RIPE) · DEALLOCATED PAApr 2, 2024abuse@m3connect.de
└ 185.15.136.8/298DE-M3CONNECT-FI-AG1-1unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.16/298DE-M3CONNECT-FI-AG2-1unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.24/298DE-M3CONNECT-FI-AG1-2unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.32/298DE-M3CONNECT-FI-AG2-2unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.40/298DE-M3CONNECT-FI-AG1-3unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.48/298DE-M3CONNECT-FI-AG2-3unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.56/298DE-M3CONNECT-FI-AG1-4unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.64/298DE-M3CONNECT-FI-AG2-4unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.72/298DE-M3CONNECT-FI-AG1-5unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.80/298DE-M3CONNECT-FI-AG2-5unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.88/298DE-M3CONNECT-FI-AG1-6unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.96/298DE-M3CONNECT-FI-AG2-6unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.104/298DE-M3CONNECT-FI-AG1-7unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.112/298DE-M3CONNECT-FI-AG2-7unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.120/298DE-M3CONNECT-FI-AG1-8unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.128/298DE-M3CONNECT-FI-AG2-8unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.136/298DE-M3CONNECT-FI-AG1-9unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.144/298DE-M3CONNECT-FI-AG2-9unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.152/298DE-M3CONNECT-FI-AG1-10unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.160/298DE-M3CONNECT-FI-AG2-10unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.168/298DE-M3CONNECT-FI-AG1-11unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.176/298DE-M3CONNECT-FI-AG2-11unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.184/298DE-M3CONNECT-FI-AG1-12unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224
└ 185.15.136.192/298DE-M3CONNECT-FI-AG2-12unknownASSIGNED PAApr 8, 2024abuse@m3connect.de
via DE-M3CONNECT-20191224

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
Rotating
First seen
Apr 2013
Current origin since
Mar 2024 · 2.6 yr
Origin networks
6
Last change of origin
Mar 2024
Recorded history

History

Handoffs
6