Latency is the amount of time that data transmission takes, from its source (such as an IoT device) to its destination.
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.
You may need to make different measurements depending on your deployment. For example, you may want to measure latency from your device to:
- The AnyNet PoP 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 as part of our connectivity managed service so IoT devices can check that they can connect to an AnyNet PoP. This service shows the latency from the device across the cellular network to the particular PoP that it is connecting to. See About the AnyNet Ping service for more information.
Measuring latency to a cloud service
Cloud services, such as AWS and Azure, provide tools to assess connectivity and latency from devices to the service in the particular region that a device connects to. Some available tools are listed below.
|Cloud service||Latency test tool|
Contact your cloud service provider for more details of the latency test tools that they offer.
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.
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
It’s important to use a reliable test tool or ping server to understand the actual latency that your devices experience.
Some public servers, such as the Google DNS service (IP address 126.96.36.199), use anycast routing. With anycast, a single IP address is shared by multiple servers in different locations, enabling a faster response to end users wherever they are located. Pinging an anycast IP address to check latency doesn’t give a true indication of how data is routed to its destination.
We recommend that you don't ping an anycast IP address to test or compare latency values.