Data as of Nov 11, 2026

69.60.231.0/24

10 residential-proxy exits · 30 days

Vianet Inc.

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
34
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BlurPath
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • GloryCloud
  • GoProxies
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYWING_BASIC
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
69.60.224.0/20
since May 2018
AS5690Residential64
8 always on
Vianet Inc.
69.60.224.0/19
since Aug 2010
AS5690Residential80
11 always on
Vianet Inc.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
69.60.224.0/198,192VIANET-INCVianet Inc. (VIANE-4) · CADirect AllocationJul 1, 2003dns@vianet.ca
└ 69.60.228.0/221,024CM-SUDBURYUnitz Online Inc. (C00740630) · CAReassignedJan 13, 2004dns@vianet.ca
via VIANET-INC

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

69.60.228.0/22

Routing history

Pattern
Stable
First seen
Aug 2013
Current origin since
Nov 2017 · 9.0 yr
Origin networks
1