Data as of Nov 20, 2026

81.30.218.0/24

5 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
5
2.0% of its addresses · 30 days
Providers
23
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

675 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • HELODATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • LOKIPROXY
  • LudaxProxy
  • NovaProxy
  • PYPROXY
  • Proxiware
  • Q2IP
  • RainProxy
  • VantageProxies
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.30.216.0/22
since Apr 2020
AS24955Residential16
1 always on
JSC "Ufanet"
81.30.192.0/19
since May 2005
AS24955Residential102
9 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.218.0 - 81.30.221.2551,024UBNJSC "Ufanet"ASSIGNED PAApr 21, 2005abuse@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
Apr 2024 · 2.6 yr
Origin networks
1