Data as of Nov 19, 2026

95.167.157.76/30

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
6
100% of its addresses · listed by providers
Always-on exits
2
33% of its exits
Providers
42
selling exits here

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.167.0.0/16
since Aug 2009
AS12389Residential1,813
932 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.167.0.0/1665,536RU-RTK-20090723PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 23, 2009abuse@rt.ru
└ 95.167.157.76/304Formula_bezopasnosti_-_DVTicket 10-19726-2ASSIGNED PAOct 5, 2010abuse@rt.ru
via RU-RTK-20090723

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
95.167.157.0/24AS12389/24RIPERPKI valid
95.167.0.0/16AS12389/16RIPEToo specific