Data as of Nov 14, 2026

136.169.216.0/22

6 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
3
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

111 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
136.169.218.0/2404
136.169.219.0/2402

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
136.169.218.0/24
since Apr 2024
AS24955Residential4JSC "Ufanet"
136.169.219.0/24
since Apr 2024
AS24955Residential2JSC "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
136.169.128.0/1732,768RU-ZAODS-20111121JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PANov 21, 2011abuse@ufanet.ru
└ 136.169.192.0/198,192UBNJSC "Ufanet"ASSIGNED PANov 23, 2011abuse@ufanet.ru
via RU-ZAODS-20111121

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

Who has announced this prefix

Summary

Routing history

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