Data as of Nov 22, 2026

125.46.51.0/24

1 residential-proxy exit · 30 days

CHINA UNICOM China169 Backbone · space held by China Unicom Henan province network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
56% of it

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
5
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • FLAMEPROXIES_BASIC
  • GEEKPROXY_FLEX
  • PROXYSCRAPE
  • Proxyma
  • SOTAPROXY

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
125.40.0.0/13
since Nov 2005
AS4837Residential5,943
23 always on
China Unicom Henan 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
125.40.0.0/13524,288UNICOM-HAChina Unicom Henan province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 125.46.51.4/304HA-PDS-DIANLISHEJIYUAN-CORPDianlishejiyuan CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.8/304HA-PDS-WANGJUNPENG-NETBARWangjunpeng NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.12/304HA-PDS-JINFANGZI-NETBARJinfangzi NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.20/304HA-PDS-XINQINGPINGGUO-NETBARXinqingpingguo NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.36/304HA-PDS-FENXIANGWANGLUO2-NETBARFENXIANGWANGLUO2 NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.44/304HA-PDS-FENXIANGWANGLUO-NETBARFenxiangwangluo NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.48/304HA-PDS-LOUYEJIANZHUFENBAO-CORPLouyejianzhufenbao CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.52/304HA-PDS-FEIDIAN2-NETBARFEIDIAN2 NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.56/298HA-PDS-DIZHENJU-BUREAUXDizhenju BureauxASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.64/304HA-PDS-MIANMAJIAGONGCHANG-CORPMianmajiagongchang CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.68/304HA-PDS-JIUTOUYA122DIAN-CORPJIUTOUYA122DIAN CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.72/304HA-PDS-JIUTOUYADONGMAICHANG-CORPJiutouyadongmaichang CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.76/304HA-PDS-JIUTOUYA119DIAN-CORPJIUTOUYA119DIAN CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.80/298HA-PDS-YONGYOURUANJIAN-CORPYongyouruanjian CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.88/304HA-PDS-GUANGBOZHONGXIN-CORPGuangbozhongxin CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.96/298HA-PDS-FEILONGWANGBA2-NETBARFEILONGWANGBA2 NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.104/304HA-PDS-JINTAIYANGYOUERYUAN-CORPJintaiyangyoueryuan CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.112/2816HA-PDS-JIAOJINGZHIDUI1-GOVJIAOJINGZHIDUI1 GOVASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.128/2816HA-PDS-JIAOJINGZHIDUI2-GOVJIAOJINGZHIDUI2 GOVASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.144/298HA-PDS-HUACHENGONGDIAN-CORPHuachengongdian CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.216/298HA-PDS-FEILONG4-NETBARFEILONG4 NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 125.46.51.240/2816HA-PDS-SHENGMAJITUAN-LTDShengmajituan LtdASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA

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

256 addresses
TypeAddressesShareRanges
Business14456%22
Residential11244%8

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2026
Current origin since
Mar 2026 · 9 mo
Origin networks
1