Data as of Nov 14, 2026

81.30.210.0/23

8 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
8
1.6% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.30.211.0/2417
81.30.210.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BottingTools
  • EZProxies
  • FastProxy
  • FlashProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LudaxProxy
  • NovaProxy
  • PrivateByte
  • Proxiware
  • ProxyEmpire
  • PuraRoute
  • Q2IP
  • RainProxy
  • RolaProxy
  • StrikeProxy
  • VantageProxies
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.30.192.0/19
since May 2005
AS24955Residential99
10 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.30.210.0/24
since Apr 2024
AS24955Residential1JSC "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.210.0/23512UBNJSC "Ufanet"ASSIGNED PANov 13, 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

81.30.208.0/22

Routing history

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