Opposition · USPTO

Opposition 91272928

OtherUSPTO

Opposition 91272928 at USPTO between Insight Direct USA, Inc. and Penguin Computing, Inc., over the mark INSIGHTHPC, filed Nov 15, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 15, 2021
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Insight Direct USA, Inc.

Company trademarks
Respondent

Penguin Computing, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the INSIGHTHPC filing.

  1. INSIGHTHPC filed

    Application 90291387 filed at the USPTO.
  2. Opposition filed

    Insight Direct USA, Inc. started opposition 91272928 at USPTO against INSIGHTHPC.
Marks

Marks involved

4 contested marks, 6 marks the challenger relies on.

MarkRoleApplicationOffice
INSIGHTHPCContested90291387USPTO
PENGUIN COMPUTING INSIGHTHPCContested90291389USPTO
INSIGHTHPCContested90291413USPTO
PENGUIN COMPUTING INSIGHTHPCContested90291419USPTO
INSIGHTRelied on74608621USPTO
INSIGHTRelied on77201689USPTO
INSIGHTRelied on77201950USPTO
INSIGHTCLOUDRelied on85175925USPTO
INSIGHTRelied on86855796USPTO
INSIGHT CONNECTED PLATFORMRelied on88936012USPTO
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_0dadba92-ee60-4e09-9953-54fcf756a52d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0dadba92-ee60-4e09-9953-54fcf756a52d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91272928",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-11-15",
  "parties": [
    {
      "name": "Insight Direct USA, Inc.",
      "role": "opponent"
    },
    {
      "name": "Penguin Computing, Inc.",
      "role": "respondent"
    }
  ]
}