Data as of Nov 21, 2026

81.30.204.0/24

2 residential-proxy exits · 30 days

JSC 'Ufanet'

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
35
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

5.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Evomi
  • FastProxy
  • GEEKPROXY_TURBO
  • GonzoProxy
  • HASDATA
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • NodeMaven
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYSAVER
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • Q2IP
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.30.204.0/22
since Apr 2020
AS24955Residential9
1 always on
JSC "Ufanet"
81.30.192.0/19
since May 2005
AS24955Residential102
8 always on
JSC "Ufanet"

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
81.30.176.0 - 81.30.223.25512,288RU-ZAODS-20020522JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 6, 2005abuse@ufanet.ru
└ 81.30.202.0 - 81.30.207.2551,536UBNJSC "Ufanet"ASSIGNED PAFeb 12, 2003abuse@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

Summary

Routing history

Pattern
Stable
First seen
Apr 2024
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1