Automated Alert: Minimal Customer Impact

What to do

• Check whether your product depends on Twilio. 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 49m it lasted.

  Anything that failed between 2026-10-30 13:53 UTC and 2026-10-30 18:42 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

1. investigatingOct 30, 2026, 1:53 PM UTC

   Our monitoring systems have detected a potential issue with verifications to Ivory Coast are being sent with an incorrect sender for customers who have not registered a sender, but messages are still being delivered without any issues. The team is investigating whether this is also happening in other countries. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

   provider

2. resolvedOct 30, 2026, 6:42 PM UTC

   We have fully investigated the issue affecting verifications to Ivory Coast, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.

   provider

Corrections

None so far.

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