Opposition · USPTO

Opposition 91286139

OtherUSPTO

Opposition 91286139 at USPTO between Asurion, LLC and uBreakiFix, Co. and Asuren LLC, over the mark ASUREN, filed Jul 19, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 19, 2023
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Asurion, LLC and uBreakiFix, Co.

Respondent

Asuren LLC

Timeline

How the case has moved

Dates from the USPTO record and the ASUREN filing.

  1. ASUREN filed

    Application 97365997 filed at the USPTO.
  2. Opposition filed

    Asurion, LLC and uBreakiFix, Co. started opposition 91286139 at USPTO against ASUREN.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
ASURENContested97365997USPTO
ASURIONRelied on76215616USPTO
ASURIONRelied on85486099USPTO
ASURIONRelied on85486112USPTO
ASURIONRelied on86828887USPTO
ASURIONRelied on87403361USPTO
ASURIONRelied on87403367USPTO
ASURIONRelied on88411735USPTO
TECHEXPRESS BY ASURIONRelied on88571819USPTO
ASURIONRelied on88979998USPTO
ASURIONRelied on88980116USPTO
ASURION HOME+Relied on88982308USPTO

+3 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_bc79c9dc-ab40-42d7-9f02-b504a4491d78
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bc79c9dc-ab40-42d7-9f02-b504a4491d78",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91286139",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-07-19",
  "parties": [
    {
      "name": "Asurion, LLC and uBreakiFix, Co.",
      "role": "opponent"
    },
    {
      "name": "Asuren LLC",
      "role": "respondent"
    }
  ]
}