Data as of Nov 18, 2026

80.67.212.0/23

6 residential-proxy exits · 30 days

Norilsk-Telecom JSC

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.67.212.0/2415
80.67.213.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
80.67.213.0/24
since Apr 2022
AS33871Residential1Norilsk-Telecom JSC

Registrations in this block

The registry's network records over this block, widest first, each 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.212.0/23512NORILSK-TELECOMNorilsk-Telecom JSC NetworkASSIGNED PAMay 4, 2005abuse@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

Who has announced 80.67.208.0/20

80.67.208.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1