Data as of Nov 14, 2026

60.8.0.0/15

No anonymizer space

CHINA UNICOM China169 Backbone · space held by China Unicom Hebei Province Network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
418
0.32% of its addresses · listed by providers
Always-on exits
10
2.4% of its exits
Spread
122 of 512
/24s with at least one exit
Providers
63
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • EnigmaProxy
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
60.8.44.0/24
since Jul 2026
AS4837ResidentialChina Unicom Hebei Province Network
60.8.77.0/24
since Dec 2025
AS4837ResidentialChina Unicom Hebei Province Network

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
60.0.0.0 - 60.10.255.255720,896UNICOM-HEChina Unicom Hebei Province NetworkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 60.8.4.128/2816weather-bureauCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.10.0/2816jianyuan-network-centerCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.12.64/2816cnc-yihaotongCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.17.128/2816power-supply-bureauCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.17.176/2816cnc-customer-service-centerCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.116.32/2816CNC-CUSTMOR-SERVICE-CENTERunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.192.64/2816BeiFang-instituteCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.196.32/2816zhi-yan-companyCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.197.16/2816jiaotongju-gaosu-guanlichuCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.224.32/2816XuanHua-steel-factoryCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.8.224.128/2732XuanHua-construction-design-instituteCNCGROUP HeBei ZhangJiaKou NetworkASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.9.247.0/24256HENGSHUI-RENMINLU8850-ZHUANXIANunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE
└ 60.9.252.0/221,024HENGSHUI-HEPINGLU8850-ZHUANXIANunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HE

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

131,072 addresses
TypeAddressesShareRanges
Residential130,368>99%18
Hosting5120.39%2
Business1920.15%11

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1