Opposition · USPTO

Opposition 91248646

OtherUSPTO

Opposition 91248646 at USPTO between Uber Technologies, Inc. and Upstylish, Inc., over the mark UBER CUTS, filed Jun 6, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 6, 2019
Marks involved
21
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Company trademarks
Respondent

Upstylish, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the UBER CUTS filing.

  1. UBER CUTS filed

    Application 88123669 filed at the USPTO.
  2. Opposition filed

    Uber Technologies, Inc. started opposition 91248646 at USPTO against UBER CUTS.
Marks

Marks involved

1 contested mark, 20 marks the challenger relies on.

MarkRoleApplicationOffice
UBER CUTSContested88123669USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBERRUSHRelied on86250398USPTO
UBER EATSRelied on86541663USPTO
UBERPOOLRelied on86645284USPTO
UBERCOMMUTERelied on86765078USPTO
UBERPOOLRelied on86984102USPTO
UBER FREIGHTRelied on87195689USPTO
UBER ELEVATERelied on87217185USPTO
UBERRelied on87256010USPTO
UBER AIRRelied on87430754USPTO

+9 more marks in this case

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_8855803d-7cd8-4fda-b4e2-76614a297393
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8855803d-7cd8-4fda-b4e2-76614a297393",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91248646",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-06-06",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Upstylish, Inc.",
      "role": "respondent"
    }
  ]
}