Skip to main content
Twilio

Some Transfer Calls in Elastic SIP Trunking Failing With Error Code 32204

Degraded Lasted 43m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
Origination US1, Origination AU1, Origination IE1, Termination US1, Termination AU1, Termination IE1
Down Index
18of 100

What to do

  • Check whether you use Twilio Origination US1, Origination AU1, Origination IE1, Termination US1 and 2 more. 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 43m it lasted.

    Anything that failed between 2026-09-24 17:19 UTC and 2026-09-24 18:02 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 5

  1. investigating

    Our monitoring systems have detected a potential issue with Voice. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

    provider

  2. investigating

    Transfer calls done via SIP REFER in Elastic SIP Trunking is Failing With Error Code 32204, our engineers are actively working on this and will provide an update in 1 hour or as soon as more information is available.

    provider

  3. investigating

    We are continuing to investigate this issue.

    provider

  4. investigating

    Transfer calls done via SIP REFER in Elastic SIP Trunking are no longer Failing With Error Code 32204, we'll monitor for 30 minutes and will share more info if it becomes available.

    provider

  5. resolved

    This incident has been resolved.

    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-e3c140c517

Is Twilio still down?

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

How long did it last?

43m, from 2026-09-24 17:19 UTC to 2026-09-24 18:02 UTC, by the times Twilio posted.

What was affected?

Twilio named Origination US1, Origination AU1, Origination IE1, Termination US1 and 2 more.

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.