Data as of Nov 12, 2026

104.166.12.0/22

11 residential-proxy exits · 30 days

Wecom LLC

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

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
104.166.13.0/2417
104.166.15.0/2404

Proxy providers listing exits

  • AnyIP
  • B2Proxy
  • ByteProxies
  • ColaProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
104.166.0.0/204,096WECOMWecom LLC (WECOM) · USDirect AllocationAug 11, 2014abuse@wecominc.com
└ 104.166.12.0/221,024WECOM-104-166-12-0Data-Max Wireless, LLC (C06255608) · USReassignedNov 10, 2016abuse@wecominc.com
via WECOM

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2015
Current origin since
Nov 2015 · 11 yr
Origin networks
1