LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

89.223.108.0/22

221 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
221
22% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
73
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

38K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.223.108.0/240111
89.223.109.0/240108

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • IPCola
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • VantageProxies
  • VitalExclusive

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.223.101.0 - 89.223.111.2552,816RU-RTK-20060919PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 29, 2020abuse@rt.ru
└ 89.223.110.0/24256rostelecom_netNoginskASSIGNED PAMay 12, 2022abuse@rt.ru
via RU-RTK-20060919

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2020
Current origin since
Jul 2020 · 6.3 yr
Origin networks
2
Last change of origin
Jul 2020
Recorded history

History

Handoffs
1