Opposition · USPTO

Opposition 91237571

OtherUSPTO

Opposition 91237571 at USPTO between ServiceNow, Inc. and Kensho Technologies Inc., over the mark KENSHO NOW, filed Nov 1, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 1, 2017
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

ServiceNow, Inc.

Company trademarks
Respondent

Kensho Technologies Inc.

Timeline

How the case has moved

Dates from the USPTO record and the KENSHO NOW filing.

  1. KENSHO NOW filed

    Application 87317949 filed at the USPTO.
  2. Opposition filed

    ServiceNow, Inc. started opposition 91237571 at USPTO against KENSHO NOW.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
KENSHO NOWContested87317949USPTO
SERVICENOWRelied on85217551USPTO
SERVICENOWRelied on85608273USPTO
KNOWLEDGERelied on85631608USPTO
KNOWLEDGERelied on85631610USPTO
NOWRelied on86008288USPTO
NOWRelied on86476476USPTO
CREATENOWRelied on86555989USPTO
STARTNOWRelied on86639340USPTO
THE END OF NO. THE BEGINNING OF NOW.Relied on86654690USPTO
SERVICENOWRelied on86665256USPTO
NOWFORUMRelied on86978025USPTO
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_7c0639cf-7a00-4c9a-8da8-639c752c17d2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7c0639cf-7a00-4c9a-8da8-639c752c17d2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91237571",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-11-01",
  "parties": [
    {
      "name": "ServiceNow, Inc.",
      "role": "opponent"
    },
    {
      "name": "Kensho Technologies Inc.",
      "role": "respondent"
    }
  ]
}