360dialog - Geschichte beachten

Meta has fully restored all affected services. This incident is now resolved.

Please refer to Meta Status Page and subscribe for updates.

Meta has resolved issues affecting some services. However, they are still actively working on restoring the remaining affected services. We are continuing to monitor the situation.

We will provide another update as soon as additional information is available from Meta.

Please refer to Meta Status Page and subscribe for updates.

Meta has resolved issues affecting some services. However, they are still actively working on restoring the remaining affected services. We are continuing to monitor the situation.

We will provide another update as soon as additional information is available from Meta.

Please refer to Meta Status Page and subscribe for updates.

We have observed a decrease in the number of errors. We are continuing to monitor the situation and are still awaiting a full fix from the Meta Engineering team.

We will provide another update as soon as additional information is available from Meta.

Please refer to Meta Status Page and subscribe for updates.

We are awaiting updates from the Meta Engineering team.

We will provide another update as soon as additional information is available from Meta.

Please refer to Meta Status Page and subscribe for updates.

Meta Engineers have confirmed they are currently experiencing high disruptions impacting the WhatsApp Cloud API.

Meta engineering teams are investigating the issue.

Please refer to Meta Status Page and subscribe for updates.

New number onboarding may be affected due to the Meta API being down.

We are following up with Meta and will share another update.

Root Cause Analysis – Messaging API Service Disruption

Date: 14 May 2026

Duration: 43 minutes

Service Affected: Messaging API (waba-v2.360dialog.io)

Summary
On 14 May 2026 between 13:26 and 14:09 UTC, the Messaging API experienced a service disruption lasting approximately 43 minutes. During this window, customers may have experienced timeouts or errors when sending messages or making API calls to waba-v2.360dialog.io. Service was fully restored at 14:09 UTC.

Outbound webhooks were not lost during the disruption. They were queued and delivered with a delay once service was restored.

Timeline (UTC)
13:26 – Service disruption begins.
14:09 – Service fully restored.

Root Cause
An infrastructure update did not behave as expected under production load. The new configuration was unable to sustain the volume of customer traffic, which led to the temporary disruption.

Resolution
Once the issue was confirmed, our engineering team applied a mitigation that restored the previous configuration. The Messaging API recovered immediately after the mitigation was in place, and we have continued to monitor the platform closely since the incident.

Preventive Measures
To reduce the likelihood and impact of similar incidents in the future, we are strengthening our infrastructure change process. This includes expanded validation prior to production rollout, more granular runtime monitoring on critical components, and a more gradual approach to applying production traffic changes.

We apologize for the disruption and any impact this may have had on your operations. We take the reliability of our platform seriously and are committed to learning from this incident.

The issue is now resolved.