Data as of Nov 14, 2026

176.208.97.0/24

5 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
34
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PacketStream
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.208.0.0/17
since Sep 2024
AS12389Residential4,418
529 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.0.0/1732,768RU-RTK-20110816PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 18, 2021abuse@rt.ru
└ 176.208.96.0/221,024LiraunknownSUB-ALLOCATED PADec 26, 2024abuse@rt.ru
via RU-RTK-20110816

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.208.96.0/22

Routing history

Pattern
Stable
First seen
Sep 2024
Current origin since
Sep 2024 · 2.2 yr
Origin networks
1