Data as of Nov 13, 2026

80.68.13.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
98% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
30
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • Evomi
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

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

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.68.0.0/204,096RU-RTK-20010523PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 16, 2015abuse@rt.ru
└ 80.68.13.184/304EducationunknownSUB-ALLOCATED PASep 28, 2023abuse@rt.ru
via RU-RTK-20010523

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
Residential25298%2
Business41.6%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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

History

Handoffs
1