Opposition · USPTO

Opposition 91300323

PendingUSPTO

Opposition 91300323 at USPTO between BuzzFeed Media Enterprises, Inc. and Bumble Holding Limited, over the mark BUZZ, filed Jul 15, 2025. Status in the office record: pending.

View BUZZGet this data via the API
Status
Pending
Filed
Jul 15, 2025
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

BuzzFeed Media Enterprises, Inc.

Respondent

Bumble Holding Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the BUZZ filing.

  1. BUZZ filed

    Application 97125147 filed at the USPTO.

  2. Opposition filed

    BuzzFeed Media Enterprises, Inc. started opposition 91300323 at USPTO against BUZZ.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
BUZZContested97125147USPTO
BUZZFEEDRelied on78862627USPTO
BUZZFEEDRelied on86050067USPTO
BUZZFEEDRelied on86403567USPTO
BUZZFEEDRelied on88597940USPTO
BUZZFEEDRelied on88598028USPTO
BUZZFEEDRelied on88599148USPTO
BUZZFEEDRelied on88600661USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_4626fea5-2bb5-4e0b-b8ad-82e1a0606686
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4626fea5-2bb5-4e0b-b8ad-82e1a0606686",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300323",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-07-15",
  "parties": [
    {
      "name": "BuzzFeed Media Enterprises, Inc.",
      "role": "opponent"
    },
    {
      "name": "Bumble Holding Limited",
      "role": "respondent"
    }
  ]
}