Turnio - Notice history

We recently made an update aimed at improving performance for message delivery and triggers. Since this change was applied earlier in the week, our monitoring has shown that the system is responding much faster and more reliably. Daily activity has been running smoothly, with no delays in triggering messages and significantly faster session start times. Most processing is now completed within milliseconds or just a few seconds, which marks a clear improvement from previous behavior. We’re continuing to monitor closely, but so far there have been no new reports of slowness. We’re pleased with the results and remain committed to making the platform even more efficient. Thank you for your continued trust and patience.

Nature of issue: We have shipped optimizations in session initialization, enhanced our monitoring of high system loads, and, since the last update, have increased overall system capacity to further improve performance and stability. Our dedicated cross-functional team is actively working on a solution to address this issue. We will share another update as soon as we have more information.

We experienced a disruption in trigger responses. The issue has been identified and reverted. The fix is currently propagating and should take effect within the next few minutes. Thank you for your patience.

Nature of issue: We have shipped optimizations in session initialization, enhanced our monitoring of high system loads, and, since the last update, have increased overall system capacity to further improve performance and stability. Our dedicated cross-functional team is actively working on a solution to address this issue. We will share another update as soon as we have more information.

Nature of issue: We have identified a bottleneck in our current Journey setup that could potentially cause delays or prevent journeys from triggering as expected during big loads in the system. Additionally, to better handle spikes in system load, we have increased our overall system capacity. Our dedicated cross-functional team is actively working on a solution to address this issue. We will share another update as soon as we have more information.

Meta has updated their Status: 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. https://metastatus.com/whatsapp-business-api

Meta is still facing disruptions with incoming messages which could potentially result in users not being able to reach out to you. We will update our status once Meta indicates a potential timeline for fix. https://metastatus.com/whatsapp-business-api

Nature of issues: Meta is currently experiencing a medium-level disruption on the WhatsApp Cloud API, affecting the reception of incoming messages, and a high-level disruption impacting WhatsApp Flows. These issues have been reported on their Status Page: https://metastatus.com/whatsapp-business-api When it started: This issue started on March 5th at 8 AM GMT. When can we expect the next update: We will provide another update within 4 hours or sooner if additional information is available.

Nature of issue: We experienced issues related to button and list presses. The issue has now been resolved.

We have identified a misbehaving customer journey that was stuck in a loop. The issue has been found and addressed. We are continuing to monitor the situation and working on improvements to prevent this from happening again.

Nature of the Issue: We are currently experiencing a system overload that is impacting the delivery of journey messages. When It Started: This issue began on February 20, 2025, at 4 PM UTC. Our engineering teams are working to add more capacity to remediate the issue. When can we expect next update: We will provide another update when additional information is available.

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

Nature of issue: We have received notification from Meta that there are some disurptions to the Cloud API. Their latest update reads as follows: "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." To follow this issue more closely, see https://metastatus.com/whatsapp-business-api When it started: This issue started on 5th of February 2025 at 08h11 UTC. When can we expect next update: We will provide another update when Meta next publishes an update. This is unfortunately an upstream issue, but we will do our best to mitigate any fallout, should it occur.

The issue has been resolved, and the application is stable again. We deeply regret any inconvenience this has caused. We’re continuing to work on improvements to prevent this from happening again Please don't hesitate to contact Turn support for assistance.

We have taken measures to optimize our infrastructure in response to changing traffic conditions. We deeply regret any inconvenience this may have caused. If you continue to experience any issues, please don’t hesitate to reach out to Turn support for assistance.

Nature of issue: We’re seeing a backlog and as a result delayed journey processing and that we’re investigating the underlying cause. When it started: This issue started on January 30th 2025 at 10am UTC -3. Our engineering teams are investigating the issue. When can we expect next update: We will provide another update when additional information is available.

The issue has been resolved, and the application is stable again. The instability was caused by an unexpected infrastructure load, which has been identified and addressed. We deeply regret any inconvenience this has caused. Should you continue to experience any problems, please don't hesitate to contact Turn support for assistance.

Nature of issue: We are currently experiencing disruptions affecting the platform's stability. You might be logged out repeatedly. Our team is working on the issue, and we hope to resolve it soon. When it started: This issue started on Jan 22nd 2025 at 18pm UTC. Our engineering teams are investigating the issue. When can we expect next update: We will provide another update when additional information is available.

The issue here was that a Redis server, a database used for fast but temporary storage, encountered occasional crashes due to memory limits being exceeded. The issue was resolved by increasing the memory limits. We were alerted to this through our automated monitoring and the issue was resolved within minutes.

We are currently experiencing some disruptions processing messages due to an internal memory database service being unresponsive. It is being reprovisioned and we expect it be resolved within the next few minutes. We will provide another update in 15 minutes if not sooner.