Data as of Nov 16, 2026

178.164.96.0/19

107 residential-proxy exits · 30 days

NTE Telekom AS

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
107
1.3% of its addresses · 30 days
Always-on exits
4
3.7% of its exits
Spread
31 of 32
/24s with at least one exit
Providers
72
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

24K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HELODATA
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.164.0.0/17
since Feb 2010
AS34087Residential349
17 always on
NTE Telekom AS

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
178.164.0.0/1732,768NO-NTETELEKOM-20100212NTE Telekom AS (ORG-NTA41-RIPE) · NOALLOCATED PADec 27, 2023abuse@nteb.no
└ 178.164.96.0/2664NTE-InternalNTE Bredband FTTH Steinkjer BeistadASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.64/2732NTE-InternalNTE Bredband FTTH Trondheim Øvre-SingsakerASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.96/2732NTE-InternalNTE Bredband FTTH Inderøy StraumenASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.128/2732NTE-InternalNTE Bredband FTTH Steinkjer ReinsvegenASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.160/2732NTE-InternalNTE Bredband FTTH Steinkjer BeistadASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.192/2816NTE-InternalNTE Bredband FTTH Namsos SkolegataASSIGNED PAAug 25, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.208/2816NTE-InternalNTE Bredband FTTH Trondheim OlderdalenASSIGNED PAMay 22, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.224/2816NTE-InternalNTE Bredband FTTH Steinkjer BeistadASSIGNED PAMay 22, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212
└ 178.164.96.240/2816NTE-InternalNTE Bredband FTTH Levanger GramyraASSIGNED PAMay 22, 2015abuse@nteb.no
via NO-NTETELEKOM-20100212

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
Dec 2015
Current origin since
Dec 2015 · 11 yr
Origin networks
1