Data as of Nov 18, 2026

81.30.212.0/22

3 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

155 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.30.212.0/2401
81.30.213.0/2401
81.30.215.0/2401

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • FastProxy
  • Geonode
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RealProxy
  • ResiProxies
  • VantageProxies

Announcements

Less specific

Covering announcements

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

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.30.214.0/24
since Apr 2024
AS24955ResidentialJSC "Ufanet"
81.30.215.0/24
since Apr 2024
AS24955Residential1JSC "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.212.0/23512UBNJSC "Ufanet"ASSIGNED PAMar 17, 2004abuse@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 2020
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1