Opposition · USPTO

Opposition 91302240

OtherUSPTO

Opposition 91302240 at USPTO between Ping Identity Corporation and WebMonitoring Technologies Inc., over the mark PING AI, filed Oct 7, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 7, 2025
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Ping Identity Corporation

Company trademarks
Respondent

WebMonitoring Technologies Inc.

Timeline

How the case has moved

Dates from the USPTO record and the PING AI filing.

  1. PING AI filed

    Application 98826539 filed at the USPTO.
  2. Opposition filed

    Ping Identity Corporation started opposition 91302240 at USPTO against PING AI.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
PING AIContested98826539USPTO
PINGACCESSRelied on85879261USPTO
PING IDENTITYRelied on86605650USPTO
PINGIDRelied on86605656USPTO
PINGDIRECTORYRelied on87890296USPTO
PING INTELLIGENT IDENTITYRelied on88460848USPTO
PINGCENTRALRelied on88576466USPTO
PING YOUNIVERSERelied on90689284USPTO
PING DAVINCIRelied on97234003USPTO
PINGAUTHORIZERelied on97239343USPTO
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_842da95f-95a3-48f0-8b2c-2af1a6b64cc5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_842da95f-95a3-48f0-8b2c-2af1a6b64cc5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302240",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-07",
  "parties": [
    {
      "name": "Ping Identity Corporation",
      "role": "opponent"
    },
    {
      "name": "WebMonitoring Technologies Inc.",
      "role": "respondent"
    }
  ]
}