Deployment
RingConn (Gen 2 / Gen 3) at China, Asia
RingConn, a Shenzhen-based Chinese smart-ring maker, is the subscription-free anchor of the biometric ring market and a deliberate counterpoint to Oura and Whoop, recorded in the biometric form factor. Its Gen 2 ring sells for about $279 with a 10-to-12-day battery and a charging case extending to about 150 days, pairing PPG, skin-temperature, blood-oxygen, and accelerometer sensors with sleep, heart-rate, and a deep-learning sleep-apnea screening feature, and all standard features are free for life with no membership, the core positioning of the brand; the Gen 2 raised about $4.4 million on Kickstarter and the Gen 3 launched in late May 2026 with more than $10 million in pre-orders in about twenty days.
Two corrections to common priors are load-bearing. First, RingConn's sleep-apnea and apnea-hypopnea-index feature is not FDA-cleared but wellness and pre-diagnostic: the company's own launch release says it is actively pursuing clearance and carries a not-intended-to-diagnose disclaimer, and the widely repeated claim that RingConn received FDA clearance for blood oxygen or sleep apnea appears only on aggregator sites and conflates it with the Happy Ring, the genuinely FDA-cleared sleep-apnea ring, so RingConn is recorded as not cleared with its 90.7-percent accuracy a vendor claim.
Second, RingConn is not subject to an active US import ban: although it was a co-respondent found to infringe in Oura's International Trade Commission case over patent 11,868,178, it settled and Oura granted it a multi-year license to keep selling in the US, so only Ultrahuman's Ring Air carries the active ban. Its clinical-validation posture is wellness-grade and claim-heavy, and its founder identity, funding, and cumulative unit shipments are not reliably verified.
RingConn (Gen 2 / Gen 3) by RingConn · Unverified · Biometric wearables
Commercial product — available for purchase in this market.
Exposure
- Customer segment
- retail
- Scale tier
- commercial 10 99
Each exposure value carries its own basis marker. Aggregators report a number; this surface preserves the source class so verification depth travels with the value.
Safety record
No incidents on record for RingConn (Gen 2 / Gen 3) at China, Asia.
Only active incidents are counted. Retracted incidents are excluded from this summary but remain reachable at their canonical URLs.
- Trust tier
- Unverifiedhow tiers work →
- Last updated
- 2026-08-20
- Company
- RingConn
- Location
- China, Asia
- Status
- operational
- Operator type
- customer deployed
- Scale at site
- 11 to 100 units
- Site environment
- indoor
- Location precision
- city centroid
- ID
6a584c51-a4fc-4c58-9cd4-cbde06021143
Timeline
- Aug 2026Current status: operational, reviewedLatest recorded state. New status transitions append here as the deployment-status recorder produces them.
On the deployment map
Operates worldwide
RingConn (Gen 2 / Gen 3) is deployed globally rather than at a single verified site, so there is no map pin.
RingConn (Gen 2 / Gen 3) operates in China, Asia. Explore the full verified map:
Methodology: Claimed (not independently verified) · no sources on file · last reviewed 2026-08-20
Verification posture
Claimed (not independently verified)
Low confidence
Review state
Stable
Last reviewed 2026-08-20
Maturity + lifecycle
Maturity stage: commercial
Lifecycle: active
Architectural position
Cohort: biometric
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for RingConn (Gen 2 / Gen 3) at China, Asia.Common questions
What is the RingConn (Gen 2 / Gen 3) deployment at China, Asia?
Who operates RingConn (Gen 2 / Gen 3) at China, Asia?
Have there been incidents at the RingConn (Gen 2 / Gen 3) deployment at China, Asia?
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.
Machine-readable surfaces
- Markdown mirror: /deployments/ringconn-gen2-china-asia.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/6a584c51-a4fc-4c58-9cd4-cbde06021143
- Data documentation: /data
- Query this programmatically: Deploy MCP