- 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 17m it lasted.
Anything that failed between 2026-07-17 15:00 UTC and 2026-07-17 15:17 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 2
- investigating
We are observing call failures to India phone numbers to Reliance Jio network. We are currently working with our carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
provider
- resolved
We are resolving this post due to it being a duplicate of an existing status.
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-ac81ca7df4
Is Twilio still down?
No, this incident was resolved 2026-07-17 15:17 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
17m, from 2026-07-17 15:00 UTC to 2026-07-17 15:17 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.