Turnio - Notice history

We have deployed a fix that ensures that webhooks are disabled and this change communicated, in order to avoid this sort of system overload again.

Messaging via webhooks experienced service interruptions yesterday due to a remote endpoint not accepting webhook deliveries at 10:08. Automated escalations alerted our support engineers to it immediately and they moved to resolve it immediately. The queue was drained and full service was restored for all customers relying on webhook deliveries for their service by 11:08. We'll be introducing a circuit breaker pattern in our webhook delivery system to guard against these situations causing message delivery problems going forward. Unfortunately, and contrary to our normal practice, this status update was posted late.

The fix for the major disruption impacting the platform has been deployed and this issue is now mitigated. Thank you for your patience.

The fix for the major disruption impacting the platform has been deployed and this issue is now mitigated. Thank you for your patience.

Nature of the issue: We are currently experiencing a major disruption impacting our system. When it started: This issue began on October 18th, 2024, at 3:00 PM UTC. Our engineering teams are actively investigating the problem. When to expect the next update: We will provide another update as soon as more information becomes available.

The fix for the major disruption impacting webhook delivery for inbound and outbound messages on WhatsApp Cloud API has been deployed by Meta and this issue is now mitigated as of 15th October 2024 5:15 AM GMT.

Nature of issue: Meta is currently experiencing a major disruption, impacting webhook delivery for inbound and outbound messages on WhatsApp Cloud API. When it started: This issue started at 15/10/2024, 07:54 AM SGT (GMT+8). When can we expect next update: We will provide another update within 1 hour or sooner if additional information is available.

Journey processing is functioning as expected.

We are experiencing delays in journey processing due to rate limiting being applied by the WhatsApp api on certain accounts. We are investigating and escalating the root causes. We will provide and update as soon as we have more details to share.