Data as of Nov 11, 2026

2.63.214.0/24

3 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
3
1.2% of its addresses · 30 days
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

712 observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.60.0.0/14
since Aug 2016
AS12389Residential47,326
523 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
2.60.0.0/14262,144RU-RTK-20101008PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 8, 2010abuse@rt.ru
└ 2.63.128.0/1732,768Rostelecom_netJSC Rostelecom . RostovSUB-ALLOCATED PAOct 7, 2021abuse@rt.ru
via RU-RTK-20101008
└ 2.63.214.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 25, 2025abuse@rt.ru
via Rostelecom_net

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