Data as of Nov 16, 2026

95.173.128.0/22

7 residential-proxy exits · 30 days

The Federal Guard Service of the Russian Federation

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
27
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

534 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.173.130.0/2404
95.173.128.0/2402
95.173.131.0/2401

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.173.128.0/21
since Aug 2009
AS8291Business9The Federal Guard Service of the Russian Federation

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
95.173.128.0/198,192RU-FGS-20090305The Federal Guard Service of the Russian Federation (ORG-TFGS1-RIPE) · RUALLOCATED PAMar 5, 2009noc@gov.ru
└ 95.173.128.0/204,096RSNETRussian State Internet NetworkASSIGNED PAMar 17, 2009noc@gov.ru
via RU-FGS-20090305

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
Oct 2013
Current origin since
Oct 2013 · 13 yr
Origin networks
1