Objective

This article shows you where Messaging Insights reports how long your messages took to send, how many are waiting in the queue, and how many failed because the queue overflowed, so you can work out why messages are arriving late.

Product

Programmable Messaging

Environment

Twilio Console

Procedure

1. In the Twilio Console, select Communications in the left sidebar.
2. Select Messaging, then Insights.
3. Select the Latency and Scale tab, then the Latency view.
4. Read the callout at the top — "Understand why message delays may be happening." — and select View guide for the full scaling, queueing and latency guide.
5. Review the two metric cards:
6. Messages currently in Queue — the count of your messages queued in Twilio at the moment the page was loaded.
7. Failed: Queue Overflowed — messages that failed with error 30001 because they could not be queued. Hover the card title for an explanation of how sending rates and the validity period cause this.
8. Review the Message Latency chart. Its description gives the total messages plotted, and the horizontal axis groups messages into latency buckets. Each bar is split into Sent (inc. Delivered, Undelivered, Delivery Unknown), Failed: Queue Overflowed and Failed: Other Reasons.
9. Select a segment of the chart, then select View List of Messages to open the messages behind it.
10. Scroll to the latency breakdown chart below. Use its controls to choose a latency range and to group the results by carrier, country, number, subaccount or Messaging Service, so you can see which senders are slowest.

Additional Information

• Messages can only stay queued for four hours before they automatically fail with error 30001. You can lower that window by setting a different validity period in your Messaging Service settings.
• The metric cards and charts follow the date range and the other filters at the top of the page.
• Messages currently in Queue is a point-in-time figure taken when the page loaded — reload the page for a fresher number.
• The breakdown chart shows a limited number of top senders; its horizontal axis title tells you how many of the total senders are displayed.
• Both latency charts can be exported with the download action on the chart card.
• When there is no matching traffic, the charts show No Results Found. If a metric cannot be loaded, the page shows "Some latency metrics could not be loaded. Please try again later." and a card falls back to a dash.
• For queue throughput over the last minutes or hour, see "How do I monitor message queue depth and throughput?".

This content was generated by AI and reviewed, edited, and verified by a human.