# Status of UDP connections (classic)
UDP is a stateless protocol and, therefore, it has no status in a strict sense. Nevertheless, to keep them similar to TCP connections, UDP connections also include a *status* field.
Because of the very nature of the UDP protocol, the status of a UDP connection does not indicate success or failure in the delivery. However, the system can deduce whether the connection is still ongoing or if it has expired. Thus, the two possible statuses of a UDP connection are:
**established**\
While events are being aggregated to the same connection (increasing its cardinality), the system considers that the connection is still open. It means the device continues sending datagrams to the same destination via the same UDP port.
**closed**\
When the aggregation time has passed and there are no new events to add to the connection, the system considers the UDP connection closed.
The aggregation time depends on your settings for aggregating events (minimum 5 minutes). Choose among 4 aggregation strategies for an optimal trade-off between detailed event information and history length. Contact [Nexthink Support](https://support.nexthink.com/) for more information.
---
# 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.nexthink.com/platform/references/references-classic/database-information-and-organization-classic/status-of-udp-connections-classic.md?ask=
```
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.