Data as of Nov 14, 2026

192.145.8.0/24

20 residential-proxy exits · 30 days

Deutsche Telekom AG · space held by m3connect GmbH

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

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Providers
27
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

572 observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BottingTools
  • Byteful
  • CatProxies
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MagneticProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
192.145.8.0/221,024DE-M3CONNECT-20181207m3connect GmbH (ORG-MG248-RIPE) · DEALLOCATED PADec 7, 2018abuse@m3connect.de
└ 192.145.8.8/304DE-M3CONNECT-BUBHANNHOTEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.12/304DE-M3CONNECT-BUBKOEFRECHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.16/304DE-M3CONNECT-BUBBRANORDHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.20/304DE-M3CONNECT-BUBLEINORDHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.24/304DE-M3CONNECT-BUBAACWUERSunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.28/304DE-M3CONNECT-BUBBOCHERNEunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.32/304DE-M3CONNECT-BUBFRANIEDERunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.36/304DE-M3CONNECT-BUBMUEMESSEunknownASSIGNED PAMar 2, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.40/304DE-M3CONNECT-BUBERLHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.48/304DE-M3CONNECT-BUBMUECITYNunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.52/304DE-M3CONNECT-BUBKOEAIRPOunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.56/304DE-M3CONNECT-BUBFRENORDHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.60/304DE-M3CONNECT-BUBFRANORDHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.64/304DE-M3CONNECT-BUBHAMALTONunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.72/304DE-M3CONNECT-BUBMAIHECHTunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.76/304DE-M3CONNECT-BUBSAAHAUPTunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.80/304DE-M3CONNECT-BUBDORMESSEunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.84/304DE-M3CONNECT-BUBOBECENTROunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.88/304DE-M3CONNECT-BUBMANHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.92/304DE-M3CONNECT-BUBAUGHOTELunknownASSIGNED PAMar 2, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.96/304DE-M3CONNECT-BUBKOBHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.100/304DE-M3CONNECT-BUBSTUCITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.104/304DE-M3CONNECT-BUBDUEAIRPOunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.108/304DE-M3CONNECT-BUBBERPOTSDunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.112/304DE-M3CONNECT-BUBNUECITYHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.116/304DE-M3CONNECT-BUBDREHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.120/304DE-M3CONNECT-BUBDARHOTELunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.124/304DE-M3CONNECT-BUBHEILHOTEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.128/304DE-M3CONNECT-BUBSTUVAIHIunknownASSIGNED PASep 23, 2022abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.132/304DE-M3CONNECT-BUBREGHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.136/304DE-M3CONNECT-BUBESSHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.140/304DE-M3CONNECT-BUBFRACITYOunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.148/304DE-M3CONNECT-BUBDUEHAUPTunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.152/304DE-M3CONNECT-BUBBREHAUPTunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.156/304DE-M3CONNECT-BUBWUEHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.160/304DE-M3CONNECT-BUBHAMHARBUunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.164/304DE-M3CONNECT-BUBWIESHOTELunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.168/304DE-M3CONNECT-BUBMOEHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.172/304DE-M3CONNECT-BUBBERAIRPOunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.176/304DE-M3CONNECT-BUBHEIDHOTEunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.180/304DE-M3CONNECT-BUBDUECITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.188/304DE-M3CONNECT-BUBOSNHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.192/304DE-M3CONNECT-BUBBERTIERGunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.196/304DE-M3CONNECT-BUBKIECITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.200/304DE-M3CONNECT-BUBULMHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.204/304DE-M3CONNECT-BUBFRAWESTHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.208/304DE-M3CONNECT-BUBFRESUEDHunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.212/304DE-M3CONNECT-BUBLUEBHOTEunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.216/304DE-M3CONNECT-BUBMUECITYWunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.220/304DE-M3CONNECT-BUBKAIHOTELunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.224/304DE-M3CONNECT-BUBKASHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.228/304DE-M3CONNECT-BUBBONHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.232/304DE-M3CONNECT-BUBBHOHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.236/304DE-M3CONNECT-BUBBIEHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.240/304DE-M3CONNECT-BUBKARHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.244/304DE-M3CONNECT-BUBMUENHAFEunknownASSIGNED PAMar 2, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.8.248/304DE-M3CONNECT-BUBWUPPERTAunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207

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 192.145.8.0/22

192.145.8.0/22

Routing history

Pattern
Stable
First seen
Aug 2019
Current origin since
Aug 2019 · 7.2 yr
Origin networks
1