Opposition · USPTO

Opposition 91291064

OtherUSPTO

Opposition 91291064 at USPTO between On Clouds GmbH and Virus International, over the mark ECO CLOUD, filed Apr 22, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 22, 2024
Marks involved
39
Parties

Who is involved

The parties as named in the office record.

Opponent

On Clouds GmbH

Company trademarks
Respondent

Virus International

Timeline

How the case has moved

Dates from the USPTO record and the ECO CLOUD filing.

  1. ECO CLOUD filed

    Application 97702998 filed at the USPTO.
  2. Opposition filed

    On Clouds GmbH started opposition 91291064 at USPTO against ECO CLOUD.
Marks

Marks involved

1 contested mark, 38 marks the challenger relies on.

MarkRoleApplicationOffice
ECO CLOUDContested97702998USPTO
CLOUDSURFERRelied on79169647USPTO
RUN ON CLOUDS.Relied on79169648USPTO
CLOUDVENTURERelied on79189498USPTO
CLOUDFLASHRelied on79199351USPTO
CLOUDFLOWRelied on79199352USPTO
CLOUDRIDERRelied on79208153USPTO
CLOUDRUSHRelied on79208154USPTO
CLOUDFLYERRelied on79211556USPTO
CLOUD XRelied on79218237USPTO
CLOUDACERelied on79233628USPTO
CLOUD EDGERelied on79235691USPTO

+27 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_ee3b7b4d-e3e0-4b67-b1b0-eeb8b318aa07
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ee3b7b4d-e3e0-4b67-b1b0-eeb8b318aa07",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91291064",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-04-22",
  "parties": [
    {
      "name": "On Clouds GmbH",
      "role": "opponent"
    },
    {
      "name": "Virus International",
      "role": "respondent"
    }
  ]
}