Opposition · USPTO

Opposition 91214343

OtherUSPTO

Opposition 91214343 at USPTO between Quantum Corporation and E. Ritter Communications Holdings, Inc., over the mark QUANTUMCLOUD, filed Jan 8, 2014. Status in the office record: other.

View QUANTUMCLOUDGet this data via the API
Status
Other
Result
Other
Filed
Jan 8, 2014
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Quantum Corporation

Company trademarks
Respondent

E. Ritter Communications Holdings, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the QUANTUMCLOUD filing.

  1. QUANTUMCLOUD filed

    Application 85681998 filed at the USPTO.

  2. Opposition filed

    Quantum Corporation started opposition 91214343 at USPTO against QUANTUMCLOUD.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
QUANTUMCLOUDContested85681998USPTO
QUANTUMRelied on72327773USPTO
QUANTUMRelied on73127739USPTO
QUANTUMRelied on74242149USPTO
QUANTUMRelied on75052261USPTO
QUANTUMRelied on75387699USPTO
QUANTUMRelied on75601999USPTO
QUANTUMRelied on75604153USPTO
QUANTUMRelied on75608837USPTO
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_f56d3c48-bcf5-41f0-b260-a96dbc549c9f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f56d3c48-bcf5-41f0-b260-a96dbc549c9f",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91214343",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-01-08",
  "parties": [
    {
      "name": "Quantum Corporation",
      "role": "opponent"
    },
    {
      "name": "E. Ritter Communications Holdings, Inc.",
      "role": "respondent"
    }
  ]
}