Cancellation · USPTO

Cancellation 92074574

OtherUSPTO

Cancellation 92074574 at USPTO between Hubbell Incorporated and Hubble Connected Limited, over the mark HUBBLE, filed Jun 24, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 24, 2020
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Petitioner

Hubbell Incorporated

Company trademarks
Respondent

Hubble Connected Limited

Timeline

How the case has moved

Dates from the USPTO record and the HUBBLE filing.

  1. HUBBLE filed

    Application 86395090 filed at the USPTO.
  2. HUBBLE registered

  3. Cancellation filed

    Hubbell Incorporated started cancellation 92074574 at USPTO against HUBBLE.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
HUBBLEContested86395090USPTO
HUBBELLRelied on72103339USPTO
HUBBELLRelied on73022132USPTO
HUBBELLRelied on73031980USPTO
HUBBELLRelied on73031981USPTO
HUBBELLRelied on73034300USPTO
HUBBELL JUNIORSRelied on73644595USPTO
HUBBELL GARDRelied on74034575USPTO
HUBBELLRelied on74526821USPTO
HUBBELLNETRelied on76393256USPTO
HUBBELL UNIVERSITYRelied on88116235USPTO
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_c052c898-522d-4176-a0b4-b1405b99bcda
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c052c898-522d-4176-a0b4-b1405b99bcda",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92074574",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-06-24",
  "parties": [
    {
      "name": "Hubbell Incorporated",
      "role": "petitioner"
    },
    {
      "name": "Hubble Connected Limited",
      "role": "respondent"
    }
  ]
}