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

112.90.136.0/21

1 residential-proxy exit · 30 days

China Unicom Guangdong IP network · space held by China Unicom Guangdong province network

Announcement
this exact prefix
RPKI valid
Announced by
AS135061
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
19
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

44 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • GSocks
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
112.88.0.0/13
since Feb 2009
AS17816Residential3,599
54 always on
China Unicom Guangdong province network
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
112.90.139.0/24
since Aug 2023
AS135061HostingChina Unicom Guangdong province network
112.90.140.0/24
since Aug 2023
AS135061HostingChina Unicom Guangdong 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
112.88.0.0/13524,288UNICOM-GDChina Unicom Guangdong province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 112.90.136.0/24256Tencent-Computer-SystemTencent-Computer-System, Shenzhen, Guangdong provinceASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 112.90.137.0/24256Tencent-Computer-SystemTencent-Computer-System, Shenzhen, Guangdong provinceASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 112.90.138.0/23512Tencent-Computer-SystemTencent-Computer-System, Shenzhen, Guangdong provinceASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD

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

Summary

Routing history

Pattern
Stable
First seen
Nov 2009
Current origin since
Apr 2023 · 3.6 yr
Origin networks
2
Last change of origin
Apr 2017
Recorded history

History

Handoffs
1