# Connection Statuses

## Types

There are four connection statuses for MMA Fight Details:

**Connected**: Connection is healthy, our onsite team have no issues and are delivering data at the lowest latency (\~2/3s from real time)

**Disconnected**: We are disconnected to our onsite team however there is an issue with the data being sent to us in real time – data will not be coming through until connection is re-established.

**Delayed**: Connection is healthy to our onsite team, but there is a known issue with latency; expect data to come through with around a \~7/8 second latency from real time.

**Unstable**: There are known issues with our connectivity to our onsite team; we’re not fully disconnected but we cannot ensure the latency of the data coming through is anywhere close to real time.

## **1. Disconnected**

This packet will be sent to indicate that we are totally disconnected to our onsite team. You will only receive this packet once – Assume that the state of the round is disconnected until you receive another “ConnectionStateChanged” packet.

### **Response Model**

#### **Disconnected Object**

| Field Name       | Type   | Description                                                     |
| ---------------- | ------ | --------------------------------------------------------------- |
| timestamp        | date   | The timestamp of the event, in UTC                              |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged” |
| state            | string | The type of state, in this case “Disconnected”                  |

### **Sample Event Packet**

```
{
    "timestamp": "2024-11-10T17:00:49.087Z",
    "eventElementType": "ConnectionStateChanged",
    "state": "Disconnected"
}Copy
```

## **2. Connected**

This packet will be sent to indicate that we are connected to our onsite team. You will only receive this packet once – Assume that the state of the round is connected until you receive another “ConnectionStateChanged” packet.

### **Respo**n**se Model**

#### **Connected Object**

| Field Name       | Type   | Description                                                     |
| ---------------- | ------ | --------------------------------------------------------------- |
| timestamp        | date   | The timestamp of the event, in UTC                              |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged” |
| state            | string | The type of state, in this case “Connected”                     |

### **Sample Event Packet**

```
{
    "timestamp": "2024-11-10T17:00:49.087Z",
    "eventElementType": "ConnectionStateChanged",
    "state": "Connected"
}

Copy
```

## **3. Delayed**

This packet will be sent to indicate that we are now in a delayed state and data from our onsite team is coming through with a known delay. You will only receive this packet once – Assume that the state of the round is delayed until you receive another “ConnectionStateChanged” packet.

### **Response Model**

#### **Connected Object**

| Field Name       | Type   | Description                                                     |
| ---------------- | ------ | --------------------------------------------------------------- |
| timestamp        | date   | The timestamp of the event, in UTC                              |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged” |
| state            | string | The type of state, in this case “Delayed”                       |

### **Sample Event Packet**

```
{
    "timestamp": "2024-11-10T17:00:49.087Z",
    "eventElementType": "ConnectionStateChanged",
    "state": "Delayed"
}Copy
```

## **4. Unstable**

This packet will be sent to indicate that we are in an unstable state with our onsite team. You will only receive this packet once – Assume that the state of the round is unstable until you receive another “ConnectionStateChanged” packet.

### **Response Model**

#### **Connected Object**

| Field Name       | Type   | Description                                                     |
| ---------------- | ------ | --------------------------------------------------------------- |
| timestamp        | date   | The timestamp of the event, in UTC                              |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged” |
| state            | string | The type of state, in this case “Unstable”                      |

### **Sample Event Packet**

```
{
    "timestamp": "2024-11-10T17:00:49.087Z",
    "eventElementType": "ConnectionStateChanged",
    "state": "Unstable"
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sportradar.com/ufc/fight-details-scenarios/connection-statuses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.