Data as of Nov 12, 2026

80.68.0.0/20

78 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
78
1.9% of its addresses · 30 days
Always-on exits
6
7.7% of its exits
Spread
13 of 16
/24s with at least one exit
Providers
71
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

21K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
80.68.0.0/21
since Jan 2016
AS21479Residential38
5 always on
PJSC Rostelecom
via OJSC Rostelecom Macroregional Branch South
80.68.8.0/22
since Jan 2016
AS21479Residential33
1 always on
PJSC Rostelecom
80.68.12.0/24
since Jul 2017
AS21479Residential2PJSC Rostelecom
80.68.13.0/24
since Jan 2016
AS21479Residential3PJSC 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.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
└ 80.68.8.0/221,024Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PADec 9, 2015abuse@rt.ru
via RU-RTK-20010523
└ 80.68.12.0/24256rostelecom-netMinistry of Information Technologies and Communication of the Rostov regionASSIGNED PADec 6, 2017abuse@rt.ru
via RU-RTK-20010523
└ 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

4,096 addresses
TypeAddressesShareRanges
Residential4,076>99%7
Business200.49%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2020
Current origin since
Jun 2020 · 6.4 yr
Origin networks
1