Opposition · USPTO

Opposition 91306145

PendingUSPTO

Opposition 91306145 at USPTO between Outreach Corporation and MyOutreach LLC, over the mark MYOUTREACH, filed Mar 25, 2026. Status in the office record: pending.

Status
Pending
Filed
Mar 25, 2026
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Outreach Corporation

Respondent

MyOutreach LLC

Timeline

How the case has moved

Dates from the USPTO record and the MYOUTREACH filing.

  1. MYOUTREACH filed

    Application 99175813 filed at the USPTO.
  2. Opposition filed

    Outreach Corporation started opposition 91306145 at USPTO against MYOUTREACH.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
MYOUTREACHContested99175813USPTO
OUTREACHRelied on86616413USPTO
OUTREACHRelied on86616418USPTO
OUTREACHRelied on88270942USPTO
OUTREACHRelied on88977522USPTO
OUTREACH ENGAGERelied on97050222USPTO
OUTREACH GUIDERelied on97050226USPTO
OUTREACH COMMITRelied on97050227USPTO
OUTREACHRelied on97304395USPTO
OUTREACHRelied on97975102USPTO
OUTREACHRelied on99418804USPTO
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_67ef4476-5ab9-49d1-bedf-62a6b8662e40
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_67ef4476-5ab9-49d1-bedf-62a6b8662e40",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306145",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-03-25",
  "parties": [
    {
      "name": "Outreach Corporation",
      "role": "opponent"
    },
    {
      "name": "MyOutreach LLC",
      "role": "respondent"
    }
  ]
}