The sending process of each message consists of 2 sub-processes:
As soon as our servers receive your message-sending request, it is sent instantly. This means that the message is promptly directed to the next station or hop in the process (e.g., the local mobile network operator where the phone number is registered) and eventually to the phone itself.
In most cases, the message is already received on the destination device before it appears in the message log.
We prioritize the sending part over the reporting part, since the sending process is time-critical. In other words, the recipient of a message should not have to wait for the reporting part to occur before receiving the message. If it takes a minute for the message to show up in your log, it doesn't mean that the message was only received on the device a minute after sending.
The reporting phase of the sending process involves creating log entries and updating the delivery status for each message and campaign.
The act of writing the log entry and updating its status can often take more time than the message-sending itself. For this reason, it is designed as an asynchronous process, meaning one operation does not wait for the other. Until delivery is confirmed (or not) by the destination, these messages will retain the status of SENT.
Sending & Delivery Speed
Considering the points mentioned above, using the information log to measure sending/delivery speed is not feasible. The only reliable method to measure speed is to track the time between the send request and the actual reception on the device, which requires access to the end device.
If you have any questions, please send an email to firstname.lastname@example.org