Data as of Nov 21, 2026

81.30.188.0/23

2 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
23
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.30.176.0/20
since Dec 2005
AS24955Residential81
9 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
81.30.189.0/24
since Oct 2025
AS24955ResidentialJSC "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.188.0/22

Routing history

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