Data as of Nov 16, 2026

62.148.131.128/25

1 residential-proxy exit · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
1
0.78% of its addresses · 30 days
Providers
36
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

64 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.148.128.0/19
since May 2005
AS15468Residential479
218 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.131.128/25128KLG_FIXED_IPSJSC CenterTelecom Kaluga branchASSIGNED PAMar 24, 2011abuse@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