Previous incidents

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...

Replacement redundancy is now also now back in place.

Meta have confirmed the update is resolved

From - https://metastatus.com/whatsapp-business-api
"We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused."

We have spoken to OVH who confirm the routing was adjusted by the upstream carrier not by them.

The API has returned to normal.

Any messages would have been queued our side and retried during the disruption.

Update from Postmark: We've deployed additional fixes and latency/errors have returned to normal performance. Engineering will continue to monitor into the evening for consistent results.