Opposition · USPTO

Opposition 91292641

OtherUSPTO

Opposition 91292641 at USPTO between Intel Corporation and Excelaca LLC, over the mark GLOBAL THREAT INTEL, filed Jul 13, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 13, 2024
Marks involved
30
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

Excelaca LLC

Timeline

How the case has moved

Dates from the USPTO record and the GLOBAL THREAT INTEL filing.

  1. GLOBAL THREAT INTEL filed

    Application 98005528 filed at the USPTO.
  2. Opposition filed

    Intel Corporation started opposition 91292641 at USPTO against GLOBAL THREAT INTEL.
Marks

Marks involved

1 contested mark, 29 marks the challenger relies on.

MarkRoleApplicationOffice
GLOBAL THREAT INTELContested98005528USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTEL INSIDERelied on74159673USPTO
INTELRelied on74225623USPTO
INTEL INSIDERelied on75160103USPTO
INTELRelied on75160105USPTO
INTELRelied on75160106USPTO
INTELRelied on75163576USPTO
INTELRelied on75349837USPTO
INTELRelied on75371362USPTO

+18 more marks in this case

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_ddfd3f00-9295-493c-ad11-cdf574d351e5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ddfd3f00-9295-493c-ad11-cdf574d351e5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292641",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-07-13",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "Excelaca LLC",
      "role": "respondent"
    }
  ]
}