Data as of Nov 20, 2026

213.228.74.0/24

62 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
62
24% of its addresses · 30 days
Providers
83
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

5.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • AETHYN_BASIC
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.228.64.0/19
since Aug 2016
AS12389Residential1,056
1 always on
PJSC Rostelecom
213.228.64.0/18
since Oct 2018
AS12389Residential1,430
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
213.228.64.0/1816,384RU-RTK-20010601PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 23, 2002abuse@rt.ru
└ 213.228.74.0/24256TC1000-DIALUPNovosibirsk Center of TelecommunicationASSIGNED PAOct 17, 2003abuse@rt.ru
via RU-RTK-20010601

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
Jun 2016
Current origin since
Aug 2016 · 10 yr
Origin networks
2
Last change of origin
Aug 2016
Recorded history

History

Handoffs
1