Opposition · USPTO

Opposition 91310832

PendingUSPTO

Opposition 91310832 at USPTO between Amazon Technologies, Inc. and Yongcheng Chen, over the mark FIRECLAW, filed Oct 1, 2026. Status in the office record: pending.

View FIRECLAWGet this data via the API
Status
Pending
Filed
Oct 1, 2026
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Amazon Technologies, Inc.

Company trademarks
Respondent

Yongcheng Chen

Timeline

How the case has moved

Dates from the USPTO record and the FIRECLAW filing.

  1. FIRECLAW filed

    Application 99718261 filed at the USPTO.

  2. Opposition filed

    Amazon Technologies, Inc. started opposition 91310832 at USPTO against FIRECLAW.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
FIRECLAWContested99718261USPTO
FIRERelied on77270887USPTO
FIRERelied on85984230USPTO
FIRERelied on85984346USPTO
FIRERelied on86748360USPTO
AMAZON FIRERelied on86982228USPTO
FIRE TV CUBERelied on88105974USPTO
FIRE TVRelied on97197338USPTO
FIRE TV OMNIRelied on97978132USPTO
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_b18dcfe0-0347-499c-913b-65f7fba6729f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b18dcfe0-0347-499c-913b-65f7fba6729f",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91310832",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-10-01",
  "parties": [
    {
      "name": "Amazon Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Yongcheng Chen",
      "role": "respondent"
    }
  ]
}