LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

60.31.147.0/24

2 residential-proxy exits · 30 days

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

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
25
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

384 observations

Proxy providers listing exits

  • 2Captcha
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
60.31.0.0/16
since May 2005
AS4837Residential171
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.147.0/298IMWHBunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.8/298IMWHWInnerMongoliaJiningHouQiWangBa1ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.8/304HouQiXingXingNetbarHouQiXingXingNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.12/304HouQiLianTongNetbarHouQiLianTongNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.16/2816IMWHWInnerMongoliaJiningHouQiWangBa2ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.16/304HouQiNetbarHouQiNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.20/304HouQiYuZhouNetbarHouQiYuZhouNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.24/304HouQiWangDaNetbarHouQiWangDaNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.28/304HouQiLianZhongNetbarHouQiLianZhongNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHW
└ 60.31.147.32/2816IMWHBunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.32/304HouQi2NetbarHouQi2NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHB
└ 60.31.147.36/304HouQiXingXingNetbarHouQiXingXingNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHB
└ 60.31.147.40/304HouQi3NetbarHouQi3NetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHB
└ 60.31.147.44/304HouQiTengFeiNetbarHouQiTengFeiNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHB
└ 60.31.147.48/298IMWHHInnerMongoliaJiningHouQiHQWLSNCASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.48/304HouQiLuoWangNetbarHouQiLuoWangNetbarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHH
└ 60.31.147.52/304HouQiSanZhongHouQiSanZhongASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via IMWHH
└ 60.31.147.56/298IMWHxunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.64/298IMWHHunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.72/298IMWHGInnerMongoliaJiningHouQiGaoQi.WangBaASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.80/298IMWHhInnerMongoliaJiningHouQihouqi.fagaiweiASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.88/298IMWHHInnerMongoliaJiningHouQiHQWLSNCASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.96/298IMWHHunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.192/298IMWHZInnerMongoliaJiningHouQiZHENGFUASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 60.31.147.200/298IMWHHunknownASSIGNED 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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