Data as of Nov 18, 2026

178.64.78.0/24

46 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
46
18% of its addresses · 30 days
Always-on exits
2
4.3% of its exits
Providers
72
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

5.4K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BUYPERSONALPROXY
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HELODATA
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.64.0.0/13
since Oct 2018
AS12389Residential67,385
2,598 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.64.0.0/13524,288RU-RTK-20100105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 5, 2010abuse@rt.ru
└ 178.64.0.0/1732,768RU-AVANGARD-DSLPJSC RostelecomASSIGNED PAJan 18, 2010abuse@rt.ru
via RU-RTK-20100105

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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
178.64.0.0/17AS12389/17RIPERPKI valid
178.64.0.0/13AS12389/23RIPERPKI valid
IRR

Route objects on 178.64.0.0/17

OriginRegistryDescriptionMaintainerModified
AS12389 RIPEOJSC "North-West Telecom"AS8997-MNTAug 18, 2016