Skip to main content
Twilio

Increased Latency and Failures on Porting APIs

Degraded Lasted 4h 20m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
PHONE NUMBERS
Down Index
21of 100

What to do

  • Check whether you use Twilio PHONE NUMBERS. 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 4h 20m it lasted.

    Anything that failed between 2026-08-19 20:38 UTC and 2026-08-20 00:58 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 7

  1. investigating

    Our monitoring systems have detected a potential issue with increased latency and failures on porting APIs. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

    provider

  2. investigating

    We are investigating intermittent latency and failures on Porting APIs. At this time customers may see 500 errors when calling the Porting APIs. We expect to provide another update in 1 hour or as soon as more information becomes available.

    provider

  3. investigating

    We are still investigating intermittent latency and failures on Porting APIs. At this time customers may continue to see 500 errors when calling the Porting APIs. We expect to provide another update in 2 hours or as soon as more information becomes available.

    provider

  4. monitoring

    The Porting APIs are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

    provider

  5. monitoring

    The Porting APIs are now operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

    provider

  6. monitoring

    The Porting APIs are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

    provider

  7. resolved

    The latency and failures been resolved and Porting APIs 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-724b101633

Is Twilio still down?

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

How long did it last?

4h 20m, from 2026-08-19 20:38 UTC to 2026-08-20 00:58 UTC, by the times Twilio posted.

What was affected?

Twilio named PHONE NUMBERS.

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.