Tranquility IP, LLC Patent litigation record

Company 11 cases

11 cases on record naming Tranquility IP, LLC: 11 as claimant, 0 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

11 cases on record

Cases on record
11
As claimant
11
As respondent
0
Patents held
Not recorded
Core tech
H04L29/06 · G06F21/31 · G06F21/43 · G06F21/44
Case no.PartiesRoleCourtFiledDurationOutcome
1:22-cv-05930 Tranquility IP, LLC v. Westermo Data Communications, Inc. Plaintiff N.D. Ill. 27 Oct 2022 113 d Voluntary dismissal
1:22-cv-01285 Tranquility IP, LLC v. Kontron America, Inc. Plaintiff D. Del. 30 Sep 2022 168 d Voluntary dismissal
6:22-cv-01012 Tranquility IP, LLC v. Schneider Pvt, Ltd. Plaintiff W.D. Tex. 28 Sep 2022 156 d Consent Judgment
3:22-cv-01925 Tranquility IP, LLC v. Tellabs Broadband, LLC Plaintiff N.D. Tex. 31 Aug 2022 125 d Voluntary dismissal
1:22-cv-02196 Tranquility IP, LLC v. NetApp, Inc. Plaintiff D. Colo. 26 Aug 2022 62 d Voluntary dismissal
1:22-cv-04565 Tranquility IP, LLC v. Cambium Networks, Inc. Plaintiff N.D. Ill. 26 Aug 2022 116 d Consent Judgment
1:22-cv-04566 Tranquility IP, LLC v. HMS Industrial Networks, Inc. Plaintiff S.D. Ill. 26 Aug 2022 63 d Voluntary dismissal
1:22-cv-00375 Tranquility IP, LLC v. Adtran, Inc. Plaintiff D. Del. 23 Mar 2022 341 d Consent Judgment
1:21-cv-01651 Tranquility IP, LLC v. ForeScout Technologies, Inc. Plaintiff D. Del. 23 Nov 2021 142 d Voluntary dismissal
1:21-cv-01652 Tranquility IP, LLC v. Fortinet, Inc. Plaintiff D. Del. 23 Nov 2021 118 d Voluntary dismissal
1:21-cv-01653 Tranquility IP, LLC v. Unify, Inc. Plaintiff D. Del. 23 Nov 2021 97 d Voluntary dismissal
Source: Patsnap Litigation Data. Cases naming Tranquility IP, LLC in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Tranquility IP is protecting

Portfolio, claim scope and where its coverage is thin. Every answer cites the records behind it.

Analyse this portfolio
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.