Opposition · USPTO

Opposition 91265427

OtherUSPTO

Opposition 91265427 at USPTO between Uber Technologies, Inc. and Robert Kocher, over the mark UNDER UBER, filed Oct 14, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 14, 2020
Marks involved
21
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Company trademarks
Respondent

Robert Kocher

Timeline

How the case has moved

Dates from the USPTO record and the UNDER UBER filing.

  1. UNDER UBER filed

    Application 88794519 filed at the USPTO.
  2. Opposition filed

    Uber Technologies, Inc. started opposition 91265427 at USPTO against UNDER UBER.
Marks

Marks involved

1 contested mark, 20 marks the challenger relies on.

MarkRoleApplicationOffice
UNDER UBERContested88794519USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBERRUSHRelied on86250398USPTO
UBER EATSRelied on86541663USPTO
UBERPOOLRelied on86645284USPTO
UBERPOOLRelied on86984102USPTO
UBER ELEVATERelied on87217185USPTO
UBERRelied on87256010USPTO
UBER AIRRelied on87430754USPTO
UBER PRESENTSRelied on87540897USPTO
UBER AI LABSRelied on87554691USPTO

+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_976ac0d9-5bdb-4c53-8020-8fadcd7e5360
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_976ac0d9-5bdb-4c53-8020-8fadcd7e5360",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91265427",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-10-14",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Robert Kocher",
      "role": "respondent"
    }
  ]
}