> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/game-hosting/game-integration/ping_beacon.md).

# Ping beacons overview

We have a core part of the i3D platform which are ping beacons. The ping beacons examine User Datagram Protocol (UDP) traffic to measure latency with a multiplayer games' UDP transport. We operate these beacons in multiple regions so that your game operates optimally. Using a ping beacon will measure the time of sending a UDP message and when you receive a response. In short, the quicker the response received, the lower the latency you have for your games.

## Why do multiplayer games use UDP versus other protocols?

User Datagram Protocol is used for multiplayer games since it allows for data transmission at a much faster rate than other protocols such as TCP.

## What is the typical flow to use ping beacons to measure latency?

Please note that you must integrate this flow using i3D SDK manually in your game clients since this is the component that sends the UDP packet towards the i3D.net ping servers. The game backend in most cases pulls the ping server list from i3D.net and passes it to the game client on start up.

1. You call the API endpoint to receive a complete list of i3D.net ping beacons.
2. Create a UDP socket.
3. Send a single UDP datagram on port 3075. The message must begin with 0xffff. **Note:** You can push other payloads in as long as it starts with 0xffff. You can add your own content.
4. Next, the ping server will reply with 0x0000.
5. From there, you can measure the time between sending the UDP message and when you receive a response.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.i3d.net/game-hosting/game-integration/ping_beacon.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
