Twilio: Voice Insights Returning Inaccurate Client Call Metrics Graphs

What to do

Check whether you use Twilio Voice Insights US1, Voice Insights AU1, Voice Insights IE1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.
Anything that failed between 2026-08-26 23:25 UTC and 2026-08-26 23:44 UTC may need a replay.
Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingAug 26, 2026, 11:25 PM UTC
Our monitoring systems have detected a potential issue with Voice Insights displaying skewed metrics in the Twilio Console. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
resolvedAug 26, 2026, 11:44 PM UTC
Twilio Voice Insights Metrics page in Console was degraded between 08/24/2026 and 08/26/2026. During this period of time customers may have experienced skewed graphs when viewing the Client Call Metrics graphs. The issue has now been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Twilio still down?

No, this incident was resolved 2026-08-26 23:44 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

20m, from 2026-08-26 23:25 UTC to 2026-08-26 23:44 UTC, by the times Twilio posted.

What was affected?

Twilio named Voice Insights US1, Voice Insights AU1, Voice Insights IE1.

What caused it?

Twilio hasn't published a root cause. If it does, it shows here.

Where does this come from?

Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.