Data as of Nov 16, 2026

185.202.32.0/21

27 residential-proxy exits · 30 days

Deutsche Telekom AG · space held by m3connect GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
27
1.3% of its addresses · 30 days
Always-on exits
2
7.4% of its exits
Spread
4 of 8
/24s with at least one exit
Providers
41
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

4.2K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • HPROXY
  • IPFly
  • IPOasis
  • InfiniteProxies
  • Kookey
  • LemonBright
  • NSocks
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • TalorData
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
185.202.38.0/24
since Oct 2025
AS209740Businessm3connect GmbH

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.202.32.0/212,048DE-M3CONNECT-20170505m3connect GmbH (ORG-MG248-RIPE) · DEALLOCATED PAAug 28, 2019abuse@m3connect.de
└ 185.202.32.0/298DE-M3CONNECT-ACCM3AACHENm3connect GmbH (ORG-MG248-RIPE) · DEASSIGNED PAJan 20, 2020abuse@m3connect.de
└ 185.202.32.64/298DE-M3CONNECT-BUBOFFKAISEunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.33.128/298DE-M3CONNECT-BUBMUCGHOTEunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.33.168/304DE-M3CONNECT-BUBAUGNORDHunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.34.80/298DE-M3CONNECT-BUBMUEMOOSAunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.34.88/298DE-M3CONNECT-BUBMUETRUDEunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.34.96/298DE-M3CONNECT-BUBMUEOLYPAunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.34.104/298DE-M3CONNECT-BUBNURCITZSunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.35.112/298DE-M3CONNECT-BUBFRAAIRPOunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.35.120/298DE-M3CONNECT-BUBMUEHAUBTunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.36.32/298DE-M3CONNECT-BUBBERCITYOunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20170505
└ 185.202.36.120/298DE-M3CONNECT-BUBNUEWESTHunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20170505

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
Jan 2020
Current origin since
Jan 2020 · 6.8 yr
Origin networks
1