DEPLOYDatabase

Incident · Other

RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)

Named alongside Ultrahuman in the same Oura '178 ITC action (337-TA-1411), RingConn resolved it on ~Oct 20 2025 via a comprehensive settlement and multi-year patent license with royalty payments to Oura, and continues selling in the US. This is the load-bearing CONTRAST to Ultrahuman: same ITC case, opposite outcomes (RingConn licensed-and-selling vs Ultrahuman excluded). Corrects the common aggregator framing that RingConn was banned.

Occurred 2025-10-20 · RingConn (Gen 2 / Gen 3) · RingConn

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)

Machine-readable surfaces

Outcomes (1)

  • regulatory actionverified

Revision history (1)

  • 2026-06-05 · outcome_class

Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.

Sources (2)

  1. Gadgets & Wearables · https://gadgetsandwearables.com/2025/10/20/ringconn-oura-lawsuit/
  2. Oura / Business Wire · https://www.businesswire.com/news/home/20250909387922/en/U.S.-International-Trade-Commission-Rules-in-Favor-of-URA-in-Patent-Case-Against-Ultrahuman-and-RingConn

Common questions

What happened in RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?
Named alongside Ultrahuman in the same Oura '178 ITC action (337-TA-1411), RingConn resolved it on ~Oct 20 2025 via a comprehensive settlement and multi-year patent license with royalty payments to Oura, and continues selling in the US. This is the load-bearing CONTRAST to Ultrahuman: same ITC case, opposite outcomes (RingConn licensed-and-selling vs Ultrahuman excluded). Corrects the common aggregator framing that RingConn was banned.
When did this incident occur?
The incident is recorded as occurring on October 20, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?
RingConn (Gen 2 / Gen 3) by RingConn is the recorded robot involved in this incident.
Has anyone responded to RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-06-24

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-06-24

Sources by quality tier

2
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for RingConn settled the Oura ITC patent case with a royalty-bearing license (avoided a ban).

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID b97e31a5-2631-4f60-a3e1-46a64dcc2269