Data as of Nov 10, 2026

178.71.42.0/24

16 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
16
6.3% of its addresses · 30 days
Always-on exits
2
13% of its exits
Providers
40
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

807 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.70.0.0/15
since Oct 2018
AS12389Residential16,495
602 always on
PJSC Rostelecom
178.64.0.0/13
since Oct 2018
AS12389Residential68,006
3,842 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
178.64.0.0/13524,288RU-RTK-20100105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 5, 2010abuse@rt.ru
└ 178.71.0.0/1665,536RU-AVANGARD-DSLOJSC "North-West Telecom"ASSIGNED PAJul 8, 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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2020
Current origin since
Mar 2020 · 6.7 yr
Origin networks
1