In this article:
The Myriota Network (Service 2) offers a median latency of 4 hours and a 90% latency of 9 hours to devices located anywhere in the world. The Myriota Network latency is continually improving as we increase the number of satellites in our constellation and further enhance our satellite capabilities.
- Median latency is the average expected latency for a message. Half of all messages will arrive in 4 hours or less.
- 90% latency is the maximum latency for 90% of messages. Nine out of ten messages will arrive in 9 hours or less.
Latency is measured from when the message is queued for transmission by the Myriota Module, to when the message is received at the device Destination. There are two key parts to latency on the Myriota Network; satellite revisit time, and satellite network to Myriota Cloud latency.
Satellite Revisit Time
The satellite revisit time is the time that it takes for a satellite to pass within clear sky view, from the time that a message is queued on the Myriota Module.
- A message is queued by the User App on the Myriota Module
- A satellite from the Myriota Network passes within clear sky view
- The message is transmitted to the satellite
Satellite Network to Myriota Cloud Latency
Once a message has been received by a satellite in the Myriota Network, that satellite must then be within clear sky view of a Myriota ground station in order to transmit the message to the Myriota Cloud.
- A message is received by the satellite
- The satellite continues on its orbital path until it comes within transmission distance of a Myriota ground station
- The satellite transmits its message payload to the Myriota ground station
- The message data is immediately processed and sent to the Myriota Cloud
- The Myriota Cloud immediately pushes the message to the device Destination
Minimising Latency
To minimise latency and ensure data is as fresh as possible:
- Your Myriota device must be deployed with a clear sky view; see the Myriota Deployment Guide for details.
- Your Myriota device must have current network information at the time of deployment; see the Update Network Information guide for details.
- Use the Module's System API, BeforeSatelliteTransmit(), to schedule message transmission (and other tasks such as sensor readings) just prior to a satellite pass.
- Don't overload the Module message queue; see the Message Queue guide for details.