Opposition · USPTO

Opposition 91310253

PendingUSPTO

Opposition 91310253 at USPTO between Thoughtworks, Inc. and Hyma Somireddy, over the mark M MONOSAGE THOUGHT WORKS, filed Sep 9, 2026. Status in the office record: pending.

Status
Pending
Filed
Sep 9, 2026
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Thoughtworks, Inc.

Company trademarks
Respondent

Hyma Somireddy

Timeline

How the case has moved

Dates from the USPTO record and the M MONOSAGE THOUGHT WORKS filing.

  1. M MONOSAGE THOUGHT WORKS filed

    Application 99501430 filed at the USPTO.
  2. Opposition filed

    Thoughtworks, Inc. started opposition 91310253 at USPTO against M MONOSAGE THOUGHT WORKS.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
M MONOSAGE THOUGHT WORKSContested99501430USPTO
THOUGHTWORKSRelied on74390270USPTO
THOUGHTWORKSRelied on75576808USPTO
THOUGHTWORKSRelied on86058220USPTO
THOUGHTWORKSRelied on86058256USPTO
/THOUGHTWORKSRelied on90877284USPTO
/THOUGHTWORKSRelied on90877288USPTO
THOUGHTWORKSRelied on98916040USPTO
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_012e6771-da8c-48bc-9db0-254ac6edd4d7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_012e6771-da8c-48bc-9db0-254ac6edd4d7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91310253",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-09-09",
  "parties": [
    {
      "name": "Thoughtworks, Inc.",
      "role": "opponent"
    },
    {
      "name": "Hyma Somireddy",
      "role": "respondent"
    }
  ]
}