engati - Notice history

The incident has been resolved

We would like to inform that the outage has now been addressed for the most part, and the API numbers have resumed functioning. We also want to provide you with a clear understanding of what happened and how 360Dialog is handling the situation. What Happened: Around 12:00 AM GMT, Meta switched from per-number webhooks to per-WABA webhooks without prior notice. 360Dialog identified the issue, alerted Meta, and began working to minimize the impact. Meta is still finalizing a permanent fix. For more details, you can refer to Meta’s official status page: Meta Status - WhatsApp Business API.

Dialog 360 has identified the cause of message delays affecting Cloud API numbers as a Meta issue and we’re awaiting their response. Meta have acknowledged this issue on their status page "Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix and the expected deployment time is in 8 hours. We will provide another update within 4 hours or sooner if additional information is available." They will try and do a fix from their end in the next 1-2 hrs while Meta figures out a long-term fix.

Message delivery works normally. Currently the error rate for "131000" is very low. We will continue to monitor the situation and provide further updates. We're still waiting for an update from Meta.

The incident has been resolved

All identified issues have been resolved, and we are actively monitoring to ensure optimal performance.