Data as of Nov 10, 2026

2.63.241.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
15
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

38 observations

Proxy providers listing exits

  • BartProxies
  • ByteProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • PuraRoute
  • RainProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.60.0.0/14
since Aug 2016
AS12389Residential47,441
542 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.241.0/24256rostelecom_netSaint-PetersburgASSIGNED PAAug 2, 2022abuse@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
Apr 2026
Current origin since
Apr 2026 · 7 mo
Origin networks
1