Turnio - Notice history

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.

Meta has 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 confirmed the outage on their Status Page: https://metastatus.com/whatsapp-business-api "We are currently experiencing major disruptions impacting message delivery on WhatsApp Business Management API."

Nature of issue: We are currently experiencing disruptions impacting our service. We suspected a major outage on WhatsApp's Cloud API. When it started: This issue started on Dec 11th, 2024 at 18:50 (UTC). Our engineering teams are monitoring the issue and Meta's Status page: https://metastatus.com/ When can we expect the next update: We will provide another update when additional information is available.

The issue has been resolved, and the application is stable again. 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.

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.