> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/monitoring-and-diagnostics/measuring-latency.md).

# Measuring latency

Latency is the time data takes to travel from its source to its destination. The source can be an IoT device.

You can assess latency using a ping test, which measures the round-trip time for a message to travel from a source to its destination and be echoed back to the source.

Your deployment may require different latency measurements. You might measure latency from your device to:

* The [AnyNet PoP](/anynet-sim/connectivity/about-eseye-pops.md) that your device connects to.
* A destination cloud service, such as AWS or Azure.
* A server at your data centre or premises.

### Measuring latency to an AnyNet PoP

The AnyNet Ping service is available through the connectivity managed service. It lets IoT devices confirm connectivity to an AnyNet PoP. The service shows latency from the device across the cellular network to its connected PoP. For more information, see [About the AnyNet Ping service](/anynet-sim/connectivity/monitoring-and-diagnostics/about-the-anynet-ping-service.md).

### Measuring latency to a cloud service

Cloud services, such as AWS and Azure, provide tools to assess device connectivity and latency within a connected region. Available tools include:

| Cloud service | Latency test tool                                                                             |
| ------------- | --------------------------------------------------------------------------------------------- |
| AWS           | [ping.psa.fun](https://ping.psa.fun) and [www.awsspeedtest.com](https://www.awsspeedtest.com) |
| Azure         | [Azure latency test](https://www.azurespeed.com/Azure/Latency)                                |

Contact your cloud service provider for details of its latency test tools.

{% hint style="info" %}
If the test runs in a browser, you may need to insert the SIM into a device such as a cellular gateway and connect a laptop to run the test.
{% endhint %}

### Measuring latency to a customer location

Check whether your infrastructure or service provider offers a latency test tool or can provide the IP address of a suitable server that your devices can ping to determine latency.

### Ping test warning

Use a reliable test tool or ping server to understand the latency your devices experience.

Some public servers use anycast routing. For example, Google DNS uses the IP address `8.8.8.8`. With anycast, multiple servers in different locations share one IP address. This enables faster responses for end users. However, pinging an anycast IP address does not show how data is routed to its destination.

Do not ping an anycast IP address to test or compare latency values.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.eseye.com/anynet-sim/connectivity/monitoring-and-diagnostics/measuring-latency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.