Data as of Nov 18, 2026

80.67.220.0/24

128 residential-proxy exits · 30 days

Norilsk-Telecom JSC

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

Residential-proxy exits

Proxy exits
128
50% of its addresses · 30 days
Always-on exits
126
98% of its exits
Providers
54
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

590K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NodeMaven
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.67.208.0/20
since May 2005
AS33871Residential163
129 always on
Norilsk-Telecom JSC

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
80.67.208.0/204,096RU-NORCOM-20040720Norilsk-Telecom JSC (ORG-NL23-RIPE) · RUALLOCATED PAJul 20, 2004abuse@sibset-team.ru
└ 80.67.215.0 - 80.67.223.2552,304NORILSK-TELECOMNorilsk-Telecom JSC NetworkASSIGNED PAMay 19, 2006abuse@sibset-team.ru
via RU-NORCOM-20040720

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
Oct 2020
Current origin since
Jan 2022 · 4.8 yr
Origin networks
1