Previous incidents

This was caused by the automatic application of a critical security update. We have adjusted the automatic security update process to ensure failover fully completes before updates are applied.

We apologise for the inconvenience caused.

This issue appears to have been resolved and calls are successfully connecting.

Service is resolved to normal levels - we have not received details from Angani yet as to the cause.

We await an RCA from Meta, but have been informed this was due to an unannounced code change at Meta which changed the way webhooks (used for incoming messages) were sent. This prevented 360dialog from receiving the messages in the correct format, and forwarding them to the correct recipient.

360Dialog setup a workaround for accounts which only had a single number on the WABA while awaiting Meta to reverse the change. The clients who only had a single number on their WABA recovered at aroun...