Data as of Nov 11, 2026

146.0.97.0/24

16 residential-proxy exits · 30 days

HL komm Telekommunikations GmbH

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
16
6.3% of its addresses · 30 days
Providers
29
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

554 observations

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FloppyData
  • GSocks
  • HideProxy
  • Infatica
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
146.0.96.0/19
since Jul 2011
AS16097Residential184HL komm Telekommunikations GmbH

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
146.0.96.0/198,192DE-TELSA-20110707HL komm Telekommunikations GmbH (ORG-HKTG1-RIPE) · DEALLOCATED PAJul 7, 2011abuse@hlkomm.de
└ 146.0.96.0/212,048HL-BUERGERNETZBuergernetz Dresden e.V.ASSIGNED PAAug 4, 2011abuse@hlkomm.de
via DE-TELSA-20110707

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

Covering aggregate above, the prefix's own history below

146.0.96.0/21

Routing history

Pattern
Stable
First seen
Feb 2017
Current origin since
Feb 2017 · 9.7 yr
Origin networks
1