Cancellation · USPTO

Cancellation 92085095

OtherUSPTO

Cancellation 92085095 at USPTO between C.D. Peacock Holdings L.L.C. and Gleeful Peacock, Inc., over the mark GLEEFUL PEACOCK, filed May 1, 2024. Status in the office record: other.

View GLEEFUL PEACOCKGet this data via the API
Status
Other
Result
Other
Filed
May 1, 2024
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Petitioner

C.D. Peacock Holdings L.L.C.

Company trademarks
Respondent

Gleeful Peacock, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the GLEEFUL PEACOCK filing.

  1. GLEEFUL PEACOCK filed

    Application 88200274 filed at the USPTO.

  2. GLEEFUL PEACOCK registered

  3. Cancellation filed

    C.D. Peacock Holdings L.L.C. started cancellation 92085095 at USPTO against GLEEFUL PEACOCK.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
GLEEFUL PEACOCKContested88200274USPTO
C. D. PEACOCKRelied on74366579USPTO
[Design mark]Relied on75098666USPTO
C.D. PEACOCKRelied on77132758USPTO
THE PEACOCK ROOM 1837Relied on97266175USPTO
HOUSE OF PEACOCKRelied on97606663USPTO
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_66d16046-2f52-4db4-8433-61fe96763f60
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_66d16046-2f52-4db4-8433-61fe96763f60",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92085095",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-05-01",
  "parties": [
    {
      "name": "C.D. Peacock Holdings L.L.C.",
      "role": "petitioner"
    },
    {
      "name": "Gleeful Peacock, Inc.",
      "role": "respondent"
    }
  ]
}