Opposition · USPTO

Opposition 91265993

OtherUSPTO

Opposition 91265993 at USPTO between Red.com, LLC and Micasense, Inc., over the mark REDEDGE-MX, filed Nov 17, 2020. Status in the office record: other.

View REDEDGE-MXGet this data via the API
Status
Other
Result
Other
Filed
Nov 17, 2020
Marks involved
25
Parties

Who is involved

The parties as named in the office record.

Opponent

Red.com, LLC

Respondent

Micasense, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the REDEDGE-MX filing.

  1. REDEDGE-MX filed

    Application 88749880 filed at the USPTO.

  2. Opposition filed

    Red.com, LLC started opposition 91265993 at USPTO against REDEDGE-MX.
Marks

Marks involved

1 contested mark, 24 marks the challenger relies on.

MarkRoleApplicationOffice
REDEDGE-MXContested88749880USPTO
RED ALERT!Relied on77323964USPTO
RED BRICKRelied on77325193USPTO
RED BRICKRelied on77498605USPTO
RED EPICRelied on77561245USPTO
RED 3DRelied on77561257USPTO
REDRelied on77668103USPTO
R3DRelied on77711436USPTO
REDCODERelied on77730795USPTO
REDCODERelied on77730802USPTO
REDSPACERelied on77732466USPTO
REDCINE-XRelied on77765440USPTO

+13 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_7f2c23e6-9d68-44ed-86d2-b83f92087abb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7f2c23e6-9d68-44ed-86d2-b83f92087abb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91265993",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-11-17",
  "parties": [
    {
      "name": "Red.com, LLC",
      "role": "opponent"
    },
    {
      "name": "Micasense, Inc.",
      "role": "respondent"
    }
  ]
}