Watermelon - Notice history

Meta has resolved the issue: "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."

Our third-party provider has implemented a workaround to restore WhatsApp messaging functionality while Meta works on a permanent resolution.

We want you to know exactly what happened and how they are handling it.

What Happened

• At around 12:00 AM GMT, Meta switched from per-number webhooks to per-WABA webhooks without prior notice.

• Our partner quickly identified the issue, alerted Meta, and began working to limit the impact.

• Meta is still finalizing a permanent fix. You can find more details on Meta’s official status page.

Partners Response

Below is how our third-party provider is addressing the impact on single-number and multiple-number WABAs:

• Single-number WABAs: They have reconfigured the setup to use per-WABA webhooks, restoring WhatsApp messaging.

• Multiple-number WABAs: They will reconfigure these accounts as soon as Meta provides a complete fix.

They have identified the cause of message delays affecting WhatsApp 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 8hours. We will provide another update within 4 hours or sooner if additional information is available."

Their engineering team is preparing a workaround to mitigate the issue for WhatsApp Business Accounts with a single number until Meta resolves the issue on their side.