Opposition 91284879
OtherUSPTO
Opposition 91284879 at USPTO between Nextiva, Inc. and Nexel Technologies Corporation, over the mark NEXEL, filed May 8, 2023. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- May 8, 2023
- Marks involved
- 19
Parties
Who is involved
The parties as named in the office record.
Respondent
Nexel Technologies Corporation
Timeline
How the case has moved
Dates from the USPTO record and the NEXEL filing.
NEXEL filed
Application 90141339 filed at the USPTO.Opposition filed
Nextiva, Inc. started opposition 91284879 at USPTO against NEXEL.
Marks
Marks involved
2 contested marks, 17 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| NEXEL | Contested | 90141339 | USPTO |
| NEXEL | Contested | 90254764 | USPTO |
| NEXTIVA | Relied on | 77634268 | USPTO |
| NEXTIVA | Relied on | 86125413 | USPTO |
| NEXTIVA OFFICE | Relied on | 86135337 | USPTO |
| NEXTIVA DRIVE | Relied on | 86346203 | USPTO |
| X | Relied on | 86849937 | USPTO |
| NEXTOS | Relied on | 87039620 | USPTO |
| NEXTIVA | Relied on | 87149716 | USPTO |
| NEXTCON | Relied on | 87242192 | USPTO |
| NEXTOS | Relied on | 87614698 | USPTO |
| NEXTIVA | Relied on | 88186231 | USPTO |
+7 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_00a33a31-8646-416e-bffc-51808f9a34ce
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_00a33a31-8646-416e-bffc-51808f9a34ce",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91284879",
"status": "other",
"office_code": "US",
"filed_date": "2023-05-08",
"parties": [
{
"name": "Nextiva, Inc.",
"role": "opponent"
},
{
"name": "Nexel Technologies Corporation",
"role": "respondent"
}
]
}