Data as of Nov 21, 2026

38.60.196.0/23

8 residential-proxy exits · 30 days

Light Node Limited · space held by Cogent Communications, LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
95 / 100 · Critical
Spamhaus DROP · Recently moved
Recent change
New origin Jun 2026
from AS138915 Kaopu Cloud HK Limited

Residential-proxy exits

Proxy exits
8
1.6% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

193 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
38.60.196.0/2405
38.60.197.0/2403

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • DataImpulse
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPFly
  • IPROCKET_PREMIUM
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeLeased fromProxy exitsHolderRPKI
38.0.0.0/8AS174Internet providerIP broker Rackdog (part)401,243
79,765 always on
Cogent Communications, LLC

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
38.0.0.0/816,777,216COGENT-ACogent Communications, LLC (COGC) · USDirect AllocationApr 16, 1991abuse@cogentco.com
└ 38.60.128.0/1732,768KAOPU-CGNT-NET-2Kaopu Cloud HK Limited (KCHL-3) · HKReallocatedDec 8, 2022whois@kaopucloud.com
└ 38.60.196.0/23512LIGHTNODE-UKLightNode-UK (C09075284) · GBReassignedDec 12, 2022whois@kaopucloud.com
via KAOPU-CGNT-NET-2

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
Rotating
First seen
Dec 2022
Current origin since
Jun 2026 · 5 mo
Origin networks
2
Last change of origin
Jun 2026
Recorded history

History

Handoffs
1