Opposition · USPTO

Opposition 91282437

OtherUSPTO

Opposition 91282437 at USPTO between On Clouds GmbH and Jiang HaoYu, over the mark CLOUD GALLOP, filed Dec 21, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 21, 2022
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

On Clouds GmbH

Company trademarks
Respondent

Jiang HaoYu

Timeline

How the case has moved

Dates from the USPTO record and the CLOUD GALLOP filing.

  1. CLOUD GALLOP filed

    Application 90859166 filed at the USPTO.
  2. Opposition filed

    On Clouds GmbH started opposition 91282437 at USPTO against CLOUD GALLOP.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
CLOUD GALLOPContested90859166USPTO
[Design mark]Relied on79139861USPTO
CLOUDRACERRelied on79169614USPTO
CLOUDSURFERRelied on79169647USPTO
RUN ON CLOUDS.Relied on79169648USPTO
CLOUDCRUISERRelied on79170270USPTO
CLOUDSTERRelied on79170308USPTO
CLOUDVENTURERelied on79189498USPTO
CLOUDFLASHRelied on79199351USPTO
CLOUDFLOWRelied on79199352USPTO
CLOUDRIDERRelied on79208153USPTO
CLOUDRUSHRelied on79208154USPTO

+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_9c52ae6c-130f-43e3-b619-ac185178d75c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9c52ae6c-130f-43e3-b619-ac185178d75c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91282437",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-12-21",
  "parties": [
    {
      "name": "On Clouds GmbH",
      "role": "opponent"
    },
    {
      "name": "Jiang HaoYu",
      "role": "respondent"
    }
  ]
}