Data as of Nov 16, 2026

89.190.248.0/24

18 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
18
7.0% of its addresses · 30 days
Providers
35
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

966 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.190.224.0/19
since Dec 2021
AS12389Residential706
1 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
89.190.224.0/198,192RU-RTK-20060614PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 14, 2006abuse@rt.ru
└ 89.190.240.0 - 89.190.248.2552,304BALTNET-NETADSL dynamic poolASSIGNED PAJun 9, 2023abuse@rt.ru
via RU-RTK-20060614

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
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1