Data as of Nov 11, 2026

95.34.0.0/16

6 residential-proxy exits · 30 days

Telenor Norge AS

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

Residential-proxy exits

Proxy exits
6
<0.01% of its addresses · 30 days
Spread
4 of 256
/24s with at least one exit
Providers
21
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

288 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.34.195.0/2403
95.34.48.0/2401
95.34.214.0/2401
95.34.232.0/2401

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • GSocks
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

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
95.34.0.0/1665,536NO-TELENOR-20081107Telenor Norge AS (ORG-NA38-RIPE) · NOALLOCATED PAApr 22, 2016abuse@telenor.net
└ 95.34.0.0/1732,768NO-TELENOR-THunknownAGGREGATED-BY-LIRMay 28, 2026abuse@telenor.net
via NO-TELENOR-20081107
└ 95.34.128.0/1732,768NO-TELENOR-THunknownAGGREGATED-BY-LIRMay 28, 2026abuse@telenor.net
via NO-TELENOR-20081107

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Nov 2008 · 18 yr
Origin networks
1