Issues with Status CallBack Webhooks for WhatsApp
Final update
We have started seeing recovery for receiving the status of outbound messages on their Status Callback webhook for WhatsApp. We will continue to monitor to ensure a full recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available. Our issue with customers not receiving the status of outbound messages on their Status Callback webhook for WhatsApp has been resolved and Status Callback webhook for WhatsApp is operating normally at this time.
Timeline
- Resolved · Mar 16, 19:19 UTC
We have started seeing recovery for receiving the status of outbound messages on their Status Callback webhook for WhatsApp. We will continue to monitor to ensure a full recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available. Our issue with customers not receiving the status of outbound messages on their Status Callback webhook for WhatsApp has been resolved and Status Callback webhook for WhatsApp is operating normally at this time.
More from Twilio
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2503:49 UTC | SMS Delivery Delays from Twilio to Claro Brazil | minor | Ongoing |
| Sep 2502:24 UTC | SMS Delivery Delays from a Subset of Twilio Short Codes to Cellularone NE Arizona United States | minor | Ongoing |
| Sep 2420:40 UTC | Event Streams Service Disruption | minor | 5h 44m |
| Sep 2417:55 UTC | SMS Delivery Receipt Delays from a Subset of Twilio Alphanumeric Sender IDs to Ooredoo Algeria | minor | Ongoing |
| Sep 2417:19 UTC | Some Transfer Calls in Elastic SIP Trunking Failing With Error Code 32204 | minor | 43m |
| Sep 2416:22 UTC | Link Branding Creation Fails with HTTP 500 Internal Server Error (Auto SSL Enabled) | minor | 2h 4m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.