Data as of Nov 19, 2026

81.30.186.0/23

4 residential-proxy exits · 30 days

JSC 'Ufanet'

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

614 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.30.187.0/2412
81.30.186.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.30.176.0/20
since Dec 2005
AS24955Residential78
9 always on
JSC "Ufanet"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.30.176.0 - 81.30.223.25512,288RU-ZAODS-20020522JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 6, 2005abuse@ufanet.ru
└ 81.30.184.0/212,048UBNJSC "Ufanet"ASSIGNED PAJun 2, 2006abuse@ufanet.ru
via RU-ZAODS-20020522

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

81.30.184.0/22

Routing history

Pattern
Stable
First seen
Apr 2020
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1