Skip to main content
Twilio

Twilio Voice has detected some customers in India receiving 480 for Outbound Calls

Degraded Lasted 9d 9h · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
Voice, APAC
Regions
apac, in

What to do

  • Check whether you use Twilio Voice, APAC in apac, in. 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 9d 9h it lasted.

    Anything that failed between 2026-03-10 15:06 UTC and 2026-03-20 00:18 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.

Updates from Twilio 16

  1. investigating

    Our monitoring systems have detected a potential issue with some customers in India receiving 480 for Outbound Calls. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

    provider

  2. investigating

    We are continuing to investigate the issue with some customers in India receiving 480 for Outbound Calls. We will provide another update in 2 hours or as soon as more information becomes available.

    provider

  3. investigating

    We are continuing to investigate the issue with some customers in India receiving 480 for Outbound Calls. We will provide another update in 4 hours or as soon as more information becomes available.

    provider

  4. investigating

    We are continuing to investigate the issue with some customers in India receiving 480 for Outbound Calls. We will provide another update in 8 hours or as soon as more information becomes available.

    provider

  5. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are currently working with our carrier partners to resolve the issue. We will try to provide another update in 8 hours or as soon as more information becomes available.

    provider

  6. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  7. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  8. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  9. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  10. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We Still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  11. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We Still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  12. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We Still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  13. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We Still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  14. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We Still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  15. identified

    We have identified the issue with some customers in India receiving 480 for Outbound Calls. We are still currently working with our carrier partners to resolve the issue. We will provide another update in 1 day or as soon as more information becomes available.

    provider

  16. resolved

    We have resolved the issue with some customers in India receiving 480 for Outbound Calls. Outbound calls are operating normally at this time.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-fb984fe8f9

Is Twilio still down?

No, this incident was resolved 2026-03-20 00:18 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

9d 9h, from 2026-03-10 15:06 UTC to 2026-03-20 00:18 UTC, by the times Twilio posted.

What was affected?

Twilio named Voice, APAC in apac, in.

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.