Data as of Nov 10, 2026

176.211.149.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
27
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

725 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.210.0.0/15
since Sep 2024
AS12389Residential18,511
70 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each 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.128.0/1732,768WEBSTREAMJSC Rostelecom regional branch "Siberia"SUB-ALLOCATED PAAug 27, 2025abuse@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

176.211.0.0/16

Routing history

Pattern
Stable
First seen
Oct 2016
Current origin since
Feb 2018 · 8.8 yr
Origin networks
1