Data as of Nov 12, 2026

146.0.98.0/23

31 residential-proxy exits · 30 days

HL komm Telekommunikations GmbH

Announcement
this exact prefix
No RPKI
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
31
6.1% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

409 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
146.0.98.0/24017
146.0.99.0/24014

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
146.0.96.0/21
since Feb 2017
AS16097Residential128HL komm Telekommunikations GmbH
146.0.96.0/19
since Jul 2011
AS16097Residential179HL komm Telekommunikations 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
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

Summary

Routing history

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