Data as of Nov 16, 2026

176.211.113.0/24

14 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
1
7.1% of its exits
Providers
52
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • StrikeProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.211.0.0/16
since Feb 2018
AS12389Residential9,382
41 always on
PJSC Rostelecom
176.210.0.0/15
since Sep 2024
AS12389Residential19,010
62 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
176.208.192.0 - 176.211.255.255212,992RU-RTK-20110816PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 18, 2021abuse@rt.ru
└ 176.211.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PANov 8, 2012abuse@rt.ru
via RU-RTK-20110816
└ 176.211.0.0/1732,768Rostelecom_netunknownSUB-ALLOCATED PAJun 15, 2022abuse@rt.ru
via RU-SIBNET

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
Mar 2024
Current origin since
Mar 2024 · 2.7 yr
Origin networks
1