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

192.145.9.0/24

15 residential-proxy exits · 30 days

Deutsche Telekom AG · space held by m3connect GmbH

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
19
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

827 observations

Proxy providers listing exits

  • AnyIP
  • B2Proxy
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • FloppyData
  • Geonode
  • InfiniteProxies
  • LemonBright
  • NovProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • RainProxy
  • Shifter
  • 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.9.0/304DE-M3CONNECT-BUBBOEHOTELunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.4/304DE-M3CONNECT-BUBLEICITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.16/304DE-M3CONNECT-BUBPADHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.20/304DE-M3CONNECT-BUBNUEHAUPTunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.24/304DE-M3CONNECT-BUBHAMNORDHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.28/304DE-M3CONNECT-BUBOLDHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.32/304DE-M3CONNECT-BUBFRAHAUPTunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.36/304DE-M3CONNECT-BUBROSTHOTEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.40/304DE-M3CONNECT-BUBKOEMESSEunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.44/304DE-M3CONNECT-BUBBERCHARLunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.48/304DE-M3CONNECT-BUBERFHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.52/304DE-M3CONNECT-BUBTRIEHOTEunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.56/304DE-M3CONNECT-BUBKONHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.60/304DE-M3CONNECT-BUBPASHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.64/304DE-M3CONNECT-BUBMUELHOTEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.68/304DE-M3CONNECT-BUBHAMCITYOunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.84/304DE-M3CONNECT-BUBDUIHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.92/304DE-M3CONNECT-BUBMAIHAUPTunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.96/304DE-M3CONNECT-BUBBRACITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.100/304DE-M3CONNECT-BUBGOECITYHunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.104/304DE-M3CONNECT-BUBBERALEXAunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.116/304DE-M3CONNECT-BUBSTUBADCAunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.120/304DE-M3CONNECT-BUBKREHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.124/304DE-M3CONNECT-BUBNEUULMHOunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.128/304DE-M3CONNECT-BUBHALSAALEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.132/304DE-M3CONNECT-BUBOFFENBURunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.136/304DE-M3CONNECT-BUBMUECITYOunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.140/304DE-M3CONNECT-BUBBREUEBERunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.152/304DE-M3CONNECT-BUBSTUAIRPOunknownASSIGNED PAFeb 4, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.160/304DE-M3CONNECT-BUBDORCITYHunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.164/304DE-M3CONNECT-BUBFULHOTELunknownASSIGNED PAJan 20, 2020abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.168/304DE-M3CONNECT-BUBBREMERHAunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.172/304DE-M3CONNECT-BUBKIEWISSEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.180/304DE-M3CONNECT-BUBMAGHOTELunknownASSIGNED PAOct 15, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.188/304DE-M3CONNECT-BUBHAMWANDSunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.196/304DE-M3CONNECT-BUBSTUZUFFEunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.200/304DE-M3CONNECT-BUBBAYHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.204/304DE-M3CONNECT-BUBTROHOTELunknownASSIGNED PAApr 13, 2021abuse@m3connect.de
via DE-M3CONNECT-20181207
└ 192.145.9.208/304DE-M3CONNECT-BUBNEUHOTELunknownASSIGNED PAApr 13, 2021abuse@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

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