Data as of Nov 19, 2026

62.148.128.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
20
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

243 observations

Proxy providers listing exits

  • ASHBURNPROXIES
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.148.128.0/19
since May 2005
AS15468Residential479
223 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.148.128.0/198,192RU-RTK-20000626PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 17, 2001abuse@rt.ru
└ 62.148.128.0/2664KALUGA-CIT-128-1JSC CenterTelecom Kaluga branchASSIGNED PAJul 16, 2004abuse@rt.ru
via RU-RTK-20000626
└ 62.148.128.64/2664KALUGA-NET128_64-127JSC CenterTelecom Kaluga branchASSIGNED PAApr 18, 2008abuse@rt.ru
via RU-RTK-20000626
└ 62.148.128.128/2664KALUGA-NET128_128-191JSC CenterTelecom Kaluga branchASSIGNED PASep 18, 2008abuse@rt.ru
via RU-RTK-20000626
└ 62.148.128.192/2664KALUGA-NET128_192-255JSC CenterTelecom Kaluga branchASSIGNED PAApr 18, 2008abuse@rt.ru
via RU-RTK-20000626

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

62.148.128.0/20

Routing history

Pattern
Stable
First seen
Nov 2013
Current origin since
Nov 2013 · 13 yr
Origin networks
1