Data as of Nov 11, 2026

80.68.0.0/24

2 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
25
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

272 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.68.0.0/20
since Jun 2020
AS12389Residential78
6 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.68.0.0/204,096RU-RTK-20010523PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 16, 2015abuse@rt.ru
└ 80.68.0.0/212,048Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthSUB-ALLOCATED PASep 28, 2023abuse@rt.ru
via RU-RTK-20010523
└ 80.68.0.48/2816EducationunknownASSIGNED PASep 28, 2023abuse@rt.ru
via Macroregional_South

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential24094%2
Business166.3%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

80.68.0.0/21

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jan 2016 · 11 yr
Origin networks
2
Last change of origin
Jan 2016
Recorded history

History

Handoffs
1