Data as of Nov 17, 2026

60.31.146.0/24

1 residential-proxy exit · 30 days

UNICOM InnerMongolia province network · space held by China Unicom Neimeng Province Network

Announcement
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
19
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GonzoProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
60.31.0.0/16
since May 2005
AS4837Residential161
1 always on
China Unicom Neimeng Province Network

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
60.31.0.0/1665,536UNICOM-NMChina Unicom Neimeng Province NetworkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 60.31.146.0/298IMWZzInnerMongoliaJiningZhongQizqwbASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.0/304ZhongQiZhengFuZhongQiZhengFuASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.4/304ZhongQiBanGongShiZhongQiBanGongShiASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.8/298IMWZzInnerMongoliaJiningZhongQizqbgw.oaASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.8/304ZhongQiErZhongZhongQiErZhongASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.12/304ZhongQiDianDianTongNetbarZhongQiDianDianTongNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.16/298IMWZzInnerMongoliaJiningZhongQizqwb1ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.16/304ZhongQiEShiDaiNetbarZhongQiEShiDaiNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.20/304ZhongQiXingGaiNianNetbarZhongQiXingGaiNianNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZz
└ 60.31.146.24/298IMWZwunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.24/304ZhongQiYiZhongZhongQiYiZhongASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.28/304ZhongQiJingXiuXueXiaoZhongQiJingXiuXueXiaoASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.32/298IMWZwunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.32/304YangGuangNetbarYangGuangNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.36/304ZhongQiYiDianTongNetbarZhongQiYiDianTongNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.40/298IMWZwunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.40/304ZhongQiXiaoJunMaNetbarZhongQiXiaoJunMaNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.44/304ZhongQiHongFangNetbarZhongQiHongFangNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWZw
└ 60.31.146.48/298IMWZKunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.56/298IMWdunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.64/298IMWZNunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.72/298IMWZZunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.80/298IMWZtunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.146.128/298IMWZhInnerMongoliaJiningZhuoZihualin.wangbaASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM

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

60.31.144.0/22

Routing history

Pattern
Stable
First seen
May 2019
Current origin since
May 2019 · 7.5 yr
Origin networks
1