Opposition 91288482
OtherUSPTO
Opposition 91288482 at USPTO between On Clouds GmbH and Lodo IP, LLC, over the mark CLOUD II, filed Nov 29, 2023. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Nov 29, 2023
- Marks involved
- 50
Parties
Who is involved
The parties as named in the office record.
Respondent
Lodo IP, LLC
Timeline
How the case has moved
Dates from the USPTO record and the CLOUD II filing.
CLOUD II filed
Application 97808514 filed at the USPTO.Opposition filed
On Clouds GmbH started opposition 91288482 at USPTO against CLOUD II.
Marks
Marks involved
1 contested mark, 49 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| CLOUD II | Contested | 97808514 | USPTO |
| [Design mark] | Relied on | 79139861 | USPTO |
| CLOUDSURFER | Relied on | 79169647 | USPTO |
| RUN ON CLOUDS. | Relied on | 79169648 | USPTO |
| CLOUDVENTURE | Relied on | 79189498 | USPTO |
| CLOUDFLASH | Relied on | 79199351 | USPTO |
| CLOUDFLOW | Relied on | 79199352 | USPTO |
| CLOUDRIDER | Relied on | 79208153 | USPTO |
| CLOUDRUSH | Relied on | 79208154 | USPTO |
| CLOUDFLYER | Relied on | 79211556 | USPTO |
| CLOUD X | Relied on | 79218237 | USPTO |
| CLOUDACE | Relied on | 79233628 | USPTO |
+38 more marks in this case
API
Get this data via the API
Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.
GET/v1/proceedings/{id}Parties, dates, outcome and every mark in the case
GET/v1/proceedings?trademark_id={trademark_id}Every proceeding on a mark
GET /v1/proceedings/{id}
ID=prc_5cbbbe8a-f718-4add-882e-ae938bd758ae
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_5cbbbe8a-f718-4add-882e-ae938bd758ae",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91288482",
"status": "other",
"office_code": "US",
"filed_date": "2023-11-29",
"parties": [
{
"name": "On Clouds GmbH",
"role": "opponent"
},
{
"name": "LODO IP, LLC",
"role": "respondent"
}
]
}