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

182.54.0.0/17

168 residential-proxy exits · 30 days

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

Announcement
this exact prefix
RPKI valid
Announced by
AS4837
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
168
0.51% of its addresses · 30 days
Spread
17 of 128
/24s with at least one exit
Providers
44
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

13K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
182.54.4.0/24039
182.54.16.0/24022
182.54.17.0/24019
182.54.111.0/24013
182.54.84.0/24013
182.54.107.0/24012
182.54.93.0/24010
182.54.113.0/2408
182.54.85.0/2407
182.54.87.0/2406
182.54.92.0/2406
182.54.86.0/2405
182.54.68.0/2404
182.54.106.0/2402
182.54.114.0/2402
182.54.110.0/2401
182.54.23.0/2401

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • HELODATA
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • VantageProxies

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
182.54.0.0/1732,768UNICOM-NXChina Unicom Ningxia Province NetworkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.4.0/221,024NX-YC-Liangtian-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.8.0/23512NX-YC-Liangtian-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.10.0/23512NX-YC-Nuanhuan-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.12.0/221,024NX-YC-Nuanhuan-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.16.0/221,024NX-YC-Jiawuyuan-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.20.0/23512NX-YC-Jiawuyuan-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.22.0/23512NX-YC-TXL-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.24.0/221,024NX-YC-TXL-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.32.0/221,024NX-GY-Xijiejifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.36.0/221,024NX-GY-Zongheloujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.40.0/212,048NX-GY-Xijiejifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.48.0/212,048NX-ZW-Zongheloujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.56.0/212,048NX-GY-Zongheloujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.64.0/221,024NX-ZW-Zongheloujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.68.0/221,024NX-ZW-Nanyuanjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.72.0/221,024NX-SZS-Zongheloujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.76.0/221,024NX-SZS-Youzhengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.80.0/221,024NX-WZ-Youzhengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.84.0/221,024NX-WZ-Youzhengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.88.0/221,024NX-WZ-Xinqujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.92.0/221,024NX-WZ-Xinqujifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.96.0/221,024NX-YC-Dianxinshangchengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.100.0/221,024NX-YC-Dianxinshangchengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.104.0/221,024NX-SZS-Youzhengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.108.0/221,024NX-SZS-Youzhengjifang-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.112.0/221,024NX-YC-KFQ-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.116.0/221,024NX-YC-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NX
└ 182.54.120.0/23512NX-YC-KFQ-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 182.54.123.0/24256NX-YC-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NX
└ 182.54.124.0/221,024NX-YC-PPPOEunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NX

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1