Opposition · USPTO

Opposition 91282769

OtherUSPTO

Opposition 91282769 at USPTO between Chubby Gorilla, Inc. and Yongkang Baojisi Electronic Commerce Co., Ltd., over the mark GORILLA TECH, filed Jan 11, 2023. Status in the office record: other.

View GORILLA TECHGet this data via the API
Status
Other
Result
Other
Filed
Jan 11, 2023
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Chubby Gorilla, Inc.

Company trademarks
Respondent

Yongkang Baojisi Electronic Commerce Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the GORILLA TECH filing.

  1. GORILLA TECH filed

    Application 97013303 filed at the USPTO.

  2. Opposition filed

    Chubby Gorilla, Inc. started opposition 91282769 at USPTO against GORILLA TECH.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
GORILLA TECHContested97013303USPTO
CHUBBY GORILLARelied on86524939USPTO
CHUBBY GORILLARelied on86900621USPTO
CHUBBY GORILLARelied on87257945USPTO
GORILLARelied on87272013USPTO
CHUBBY GORILLARelied on88373580USPTO
CHUBBY GORILLARelied on88374056USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_78eb6f5a-c7ab-4e29-816d-cf9283053f31
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_78eb6f5a-c7ab-4e29-816d-cf9283053f31",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91282769",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-01-11",
  "parties": [
    {
      "name": "Chubby Gorilla, Inc.",
      "role": "opponent"
    },
    {
      "name": "Yongkang Baojisi Electronic Commerce Co., Ltd.",
      "role": "respondent"
    }
  ]
}