Opposition · USPTO

Opposition 91309031

SuspendedUSPTO

Opposition 91309031 at USPTO between Deutsche Telekom AG and Trible AI, Inc., over the mark T., filed Jul 22, 2026. Status in the office record: suspended.

Status
Suspended
Filed
Jul 22, 2026
Marks involved
34
Parties

Who is involved

The parties as named in the office record.

Opponent

Deutsche Telekom AG

Company trademarks
Respondent

Trible AI, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the T. filing.

  1. T. filed

    Application 99428567 filed at the USPTO.
  2. Opposition filed

    Deutsche Telekom AG started opposition 91309031 at USPTO against T..
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 33 marks the challenger relies on.

MarkRoleApplicationOffice
T.Contested99428567USPTO
TRelied on74720652USPTO
TRelied on74720656USPTO
T-MOBILERelied on75093051USPTO
T-SYSTEMRelied on75093059USPTO
T MOBILERelied on75095186USPTO
T-MOBILERelied on75248964USPTO
T-SYSTEMSRelied on76166309USPTO
TRelied on76252927USPTO
T-MOBILE USARelied on76350166USPTO
TRelied on77307279USPTO
T MOBILERelied on77311132USPTO

+22 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_c9e9ed45-8380-4662-a9f5-4037c51dfca2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c9e9ed45-8380-4662-a9f5-4037c51dfca2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91309031",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2026-07-22",
  "parties": [
    {
      "name": "Deutsche Telekom AG",
      "role": "opponent"
    },
    {
      "name": "Trible AI, Inc.",
      "role": "respondent"
    }
  ]
}