Refreshed
Welcome to the Turn.io status page. We will update any changes to system performance here. Subscribe to updates to receive email notifications.
Uptime 17 days 16 hours 14 minutes 16 seconds
Started:
Ended:
Length:
Started:
Ended:
Length:
Started:
Ended:
Length:
Started:
Ended:
Length:
Started:
Ended:
Length:
Scheduled | Jun 25, 2025 22:00 - Jun 26, 2025 00:00 | GMT+02:00
Routine system maintenance will be performed on Wednesday 25 June 2025. As a result service disruption may occur impacting all customers on app.turn.io. Private cloud customers will not be impacted.
What you need to know:
- During this time reduced availability of the Turn.io web application should be expected.
- During this time a delay in message delivery should be expected.
Resolved | Jun 12, 2025 | 23:37 GMT+02:00
The login issues caused by the Google Cloud Platform outage are no longer affecting access to Turn.io. Users should now be able to log in without any problems.
We’ll continue monitoring the situation closely. If you’re still experiencing issues or need any assistance, please don’t hesitate to reach out to our support team.
Monitoring | Jun 12, 2025 | 20:46 GMT+02:00
We are currently experiencing partial login issues on Turn.io due to an ongoing incident affecting several Google Cloud Platform services, including:
- Google Cloud Dataproc
- Google Cloud Storage
- Identity and Access Management (IAM)
As a result, some users may encounter difficulties logging into the platform. This issue is not affecting all users.
We are closely monitoring the situation and will provide updates as soon as more information becomes available. You can also follow Google’s status updates here: https://status.cloud.google.com/regional/europe
Thank you for your patience.
Resolved | May 30, 2025 | 12:42 GMT+02:00
All email reminders, webhook alerts, and export insights are working again on all environment.
Resolution in progress | May 30, 2025 | 11:02 GMT+02:00
All email reminders, webhook alerts, and export insights are working again on the shared environment. Updates to private clouds currently being rolled out.
Resolved | May 28, 2025 | 21:08 GMT+02:00
This incident has been fully resolved.
We experienced delays in processing incoming messages and automated journeys due to inefficient search infrastructure operations that were slowing down our platform. Our engineering team identified and fixed the underlying performance issues throughout the day.
All services are now operating normally and message processing has returned to expected speeds.
We apologize for any delays you may have experienced with your messaging and automation today.
Resolution in progress | May 28, 2025 | 14:52 GMT+02:00
We're still seeing occasional delays occur and we're doing further investigation as to the underlying causes.
Monitoring | May 28, 2025 | 12:40 GMT+02:00
We have released a fix to address the database operation which was causing delays. Things are looking stable again and the system is performing as expected. We will continue to monitor the situation.
Investigating | May 28, 2025 | 10:24 GMT+02:00
Recent performance improvements work has changed how updates happen to contact information. We suspect that as a side effect of this, it is highlighting an un-optimised database operation which could be causing a degradation in system performance. We are still investigating and observing.
Resolved | May 15, 2025 | 18:14 GMT+02:00
The issue has been resolved, the application is stable again.
The instability was caused by an unexpected infrastructure load, which has been identified and addressed.
Open | May 15, 2025 | 18:01 GMT+02:00
When can we expect next update:
We will provide another update when additional information is available.
Resolved | May 01, 2025 | 19:30 GMT+02:00
We are continuing to investigate the cause of chats and the contact details sidebar loading slowly in the helpdesk.
We will provide another update when additional information is available.
We traced the degradation to extra queries triggered when listing templated messages. A fix was launched and chat loading performance has returned to normal.
Resolved | Apr 03, 2025 | 18:43 GMT+02:00
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.
Monitoring | Mar 27, 2025 | 21:57 GMT+01:00
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.
Resolution in progress | Mar 27, 2025 | 20:19 GMT+01:00
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.
Monitoring | Mar 24, 2025 | 17:18 GMT+01:00
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.
Investigating | Mar 20, 2025 | 16:06 GMT+01:00
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.
Resolved | Mar 12, 2025 | 22:11 GMT+01:00
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
Resolution in progress | Mar 11, 2025 | 21:39 GMT+01:00
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
Identified | Mar 11, 2025 | 20:16 GMT+01:00
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.
Resolved | Mar 04, 2025 | 20:45 GMT+01:00
Nature of issue:
We experienced issues related to button and list presses. The issue has now been resolved.
Resolved | Feb 20, 2025 | 18:11 GMT+01:00
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.
Resolution in progress | Feb 20, 2025 | 17:16 GMT+01:00
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.
Resolved | Feb 05, 2025 | 16:36 GMT+01:00
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.
Open | Feb 05, 2025 | 09:11 GMT+01:00
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.
Resolved | Jan 30, 2025 | 21:11 GMT+01:00
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.
Monitoring | Jan 30, 2025 | 16:30 GMT+01:00
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.
Open | Jan 30, 2025 | 10:10 GMT+01:00
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.
Resolved | Jan 22, 2025 | 20:28 GMT+01:00
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.
Investigating | Jan 22, 2025 | 20:03 GMT+01:00
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.
Resolved | Jan 08, 2025 | 15:03 GMT+01:00
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.
Monitoring | Jan 08, 2025 | 15:08 GMT+01:00
The infrastructure problem has been resolved. We are continuing to monitor the situation.
Open | Jan 08, 2025 | 14:48 GMT+01:00
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.
Resolved | Dec 12, 2024 | 02:03 GMT+01:00
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
Identified | Dec 11, 2024 | 20:01 GMT+01:00
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."
Open | Dec 11, 2024 | 19:54 GMT+01:00
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.
Resolved | Dec 05, 2024 | 19:31 GMT+01:00
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.
Resolved | Nov 27, 2024 | 12:28 GMT+01:00
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.
Monitoring | Nov 19, 2024 | 10:08 GMT+01:00
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.
Resolved | Nov 18, 2024 | 21:02 GMT+01:00
The fix for the major disruption impacting the platform has been deployed and this issue is now mitigated.
Thank you for your patience.
Resolved | Oct 18, 2024 | 17:51 GMT+02:00
The fix for the major disruption impacting the platform has been deployed and this issue is now mitigated.
Thank you for your patience.
Investigating | Oct 18, 2024 | 17:29 GMT+02:00
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.
Resolved | Oct 15, 2024 | 03:15 GMT+02:00
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.
Open | Oct 15, 2024 | 01:54 GMT+02:00
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.
Resolved | Oct 06, 2024 | 22:19 GMT+02:00
Journey processing is functioning as expected.
Open | Oct 06, 2024 | 13:49 GMT+02:00
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.
Resolved | Aug 09, 2024 | 12:15 GMT+02:00
Nature of issue:
A previously reported issue impacting journey triggers was resolved. This issue started on August 9th 2024 at 01:00 am GMT +1 and a fix was deployed at August 9th 2024 at 11:15 GMT +1. The fix has resolved the issue and we have continued to monitor the situation until now.
Resolved | Aug 01, 2024 | 21:01 GMT+02:00
The issue is resolved.
The slowness was due to an unexpected infrastructure load on the primary database. The reason for that load was identified and removed.
Monitoring | Aug 01, 2024 | 20:14 GMT+02:00
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.
Investigating | Aug 01, 2024 | 18:45 GMT+02:00
Nature of issue:
We are currently experiencing some timeouts in message processing.
When it started:
This issue started on Aug 1st, 2024 at 03:00 PM GMT +1. Our engineering teams are investigating the issue.
When can we expect the next update:
We will provide another update when additional information is available.
Resolved | Jul 23, 2024 | 19:44 GMT+02:00
The team identified the inbox stats caching query as causing the unexpected lock and took immediate steps to improve the query execution. A code revert was then applied to get the application back to a stable condition.
We're continuing to work on improvements to prevent this from happening in the future.
Monitoring | Jul 22, 2024 | 19:09 GMT+02:00
We have launched a fix and we are now monitoring the performance.
When can we expect next update
We will provide another update when additional information is available.
Investigating | Jul 22, 2024 | 14:58 GMT+02:00
A fix has been deployed but we’re observing above-average delays in journey completion times and we’re investigating that.
When can we expect next update
We will provide another update when additional information is available.
Resolution in progress | Jul 22, 2024 | 09:53 GMT+02:00
Nature of issue:
We had previously identified an issue with the platform functionalities including login. Our engineering teams had identified the issue previously and deployed a fix. The issue seems to have occurred again and we are continuing our efforts in resolving this.
When can we expect next update:
We will provide another update when additional information is available.
Resolved | Jul 08, 2024 | 16:05 GMT+02:00
A fix has been deployed.
We are currently monitoring it.
Investigating | Jul 08, 2024 | 15:33 GMT+02:00
We have identified an issue with the People feature. The page fails to load.
The above issue is impacting some customers on our shared cluster at https://whatsapp.turn.io. It may cause slowness to the platform and affect all customers.
We are sorry for the inconvenience and are working to resolve the issue as quickly as possible.
Resolved | Jun 27, 2024 | 14:29 GMT+02:00
The fix for the major disruption impacting messaging templates on WhatsApp Business Management API has been deployed and this issue is now resolved as of 11:00 GMT.
Thank you for your patience.
Resolution in progress | Jun 26, 2024 | 19:35 GMT+02:00
Meta's engineering teams have identified the root cause of the disruption impacting messaging templates on WhatsApp Business Management APIs. They are currently deploying the fix.
https://metastatus.com/whatsapp-business-api
We will keep you updated about the progress.
Identified | Jun 26, 2024 | 15:11 GMT+02:00
Meta is experiencing some disruption impacting messaging templates on WhatsApp Business Management APIs.
This issue started on Jun 26 2024 6:35 AM GMT-3 reported at https://metastatus.com/whatsapp-business-api
We are monitoring the situation and update you as soon as the Meta team has resolved the issue.
Resolved | Jun 11, 2024 | 08:10 GMT+02:00
A fix to address slowness on the Turn platform has been released, additionally the "lease not found" errors have been addressed. This issue is now mitigated. Thank you for your patience.
Resolution in progress | Jun 05, 2024 | 21:59 GMT+02:00
We have identified the root cause of the slowness. We have increased the throughput capacity of our systems to deal with slowdowns in responses, while we address the underlying issue.
Resolution in progress | Jun 05, 2024 | 16:06 GMT+02:00
The issue with journeys not responding have been identified and the team is actively working on a resolution.
Investigating | Jun 05, 2024 | 15:52 GMT+02:00
The issue with journeys not responding have been identified and the team is actively working on a resolution.
Monitoring | Jun 04, 2024 | 16:23 GMT+02:00
The issue is solved and journeys returned to work as expected for now.
We are currently monitoring it.
Open | Jun 04, 2024 | 16:13 GMT+02:00
We have identified an issue with message deliveries. Journeys fail to trigger or respond to interaction.
The above issue is impacting some customers.
We are working to resolve the issue as quickly as possible.
Resolved | May 31, 2024 | 08:56 GMT+02:00
Webhooks are functioning as expected.
Open | May 31, 2024 | 08:28 GMT+02:00
We have identified an issue with Webhooks not receiving events or sending multiple messages. The above issue is impacting some customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
We are working to resolve the issue as quickly as possible.
Resolved | May 22, 2024 | 10:50 GMT+02:00
Issue has been resolved
Resolved | Apr 30, 2024 | 15:34 GMT+02:00
The issue with collections has been resolved and organizations should be able to view their collections again.
Resolution in progress | Apr 30, 2024 | 13:45 GMT+02:00
There is currently an ongoing issue with the Collections on helpdesk and some Turn SaaS accounts are unable to see their collections.
We have identified the issue and are looking to release a fix shortly.
Resolved | Apr 26, 2024 | 07:26 GMT+02:00
The issue impacting message delivery is resolved now.
Open | Apr 26, 2024 | 06:19 GMT+02:00
We have identified an issue that impacts message delivery for all clients on Turn Saas cluster.
Our engineers are looking into it.
Resolved | Apr 11, 2024 | 15:19 GMT+02:00
The fix for the major disruption impacting message delivery on Meta Cloud API has been deployed and this issue is now mitigated as of April 11th 4:30AM GMT.
Thank you for your patience.
Reference: https://metastatus.com/whatsapp-business-api
Identified | Apr 11, 2024 | 13:11 GMT+02:00
We had identified an issue with Meta business products experiencing an outage.
Reference: https://metastatus.com/
Resolved | Apr 08, 2024 | 18:55 GMT+02:00
All issues have been resolved and Turn is working as expected.
Investigating | Apr 08, 2024 | 18:50 GMT+02:00
We have identified an issue with the Turn WebApp UI. Turn's web page fails to load or update in the browser.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are also affected.
Please note that the messaging service is not affected.
We are working to resolve the issue as quickly as possible.
Resolved | Apr 03, 2024 | 23:30 GMT+02:00
The issue is resolved by Meta engineering team.
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.
Identified | Apr 03, 2024 | 20:54 GMT+02:00
Meta is experiencing a significant disruption that affects the delivery of messages for all numbers via the Cloud API and On-Premise API. This issue started on 04-03-2024 at 11:18 AM PST.
We are monitoring the situation and update you as soon as the Meta team has resolved the issue.
Reference: https://metastatus.com/
Resolved | Mar 27, 2024 | 11:24 GMT+01:00
The issue is resolved.
Monitoring | Mar 27, 2024 | 05:24 GMT+01:00
The issue is resolved by Meta engineering team. We are monitoring our systems.
Open | Mar 27, 2024 | 04:46 GMT+01:00
Meta is experiencing a significant disruption that affects the delivery of messages for all numbers via the Cloud API. This issue started at March 26, 2024, 7:55:47 PM PDT.
We are monitoring the situation and update as soon as Meta team has resolved the issue.
Resolved | Mar 06, 2024 | 06:41 GMT+01:00
We had identified an issue with Meta business products experiencing an outage. Reference: https://metastatus.com/
Meta has now resolved the issue.
Monitoring | Mar 05, 2024 | 19:54 GMT+01:00
https://metastatus.com/
We will keep you informed as soon as Meta establishes the status of their products.
Open | Mar 05, 2024 | 17:37 GMT+01:00
We have identified that Meta business products are experiencing an outage. Reference: https://metastatus.com/
The above issue is affecting campaigns, local storage, and signups.
Customers on our shared cluster at https://whatsapp.turn.io and Private Cloud customers are also experiencing disruptions.
We will keep you informed as soon as Meta establishes the status of their products.
Resolved | Feb 27, 2024 | 19:35 GMT+01:00
Fixed routing for sandboxes on Cloud API.
Resolution in progress | Feb 27, 2024 | 14:44 GMT+01:00
We have identified an issue with the Sandbox accounts.
Sandboxes are not working as expected.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
We are working to resolve the issue as quickly as possible.
Resolved | Jan 29, 2024 | 11:24 GMT+01:00
The Meta support team has confirmed the resolution of the message delivery issue.
We deeply regret any inconvenience this has caused. Should you continue to experience any problems, please don't hesitate to contact Turn support or your impact partnership manager for assistance..
Resolution in progress | Jan 29, 2024 | 10:11 GMT+01:00
Meta's support and billing engineers have identified the root cause and are working on a resolution. The outage relates to recent billing changes applied by Meta that are in conflict with our account setup as a WhatsApp impact service provider.
We will update this status page as soon as we have more information.
We sincerely apologise for this interruption in service. Please feel free to reach out to your Impact Partners at Turn should your service be impacted.
Open | Jan 27, 2024 | 16:58 GMT+01:00
We've noticed some problems with messages reaching users. Our engineering team is actively working on resolving this. Additionally, we've reached out to Meta to check if there might be any related issues on their end.
Resolved | Jan 23, 2024 | 07:00 GMT+01:00
The Reminders queueing issue has been resolved, we will keep monitoring it.
Resolution in progress | Jan 22, 2024 | 19:49 GMT+01:00
We have identified an issue with the Reminders feature. Reminders are getting stuck in queued status.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
We are working to resolve the issue as quickly as possible.
Resolved | Dec 06, 2023 | 07:10 GMT+01:00
The server in question has been replaced and services are operating normally again.
Open | Dec 06, 2023 | 06:44 GMT+01:00
One of the servers, responsible for 2-3% of the workload, is under performing due to it running out of memory for the work assigned to it. This is causing some numbers to be offline. It is being replaced and extra capacity is being provisioned.
Resolved | Nov 21, 2023 | 20:45 GMT+01:00
All issues have been resolved and Turn is working as expected.
Identified | Nov 21, 2023 | 20:07 GMT+01:00
The repairs are taking longer than anticipated, we're creating extra capacity to give the platform redundant capacity while repairs are taking place.
Open | Nov 21, 2023 | 19:54 GMT+01:00
Our underlying managed infrastructure is undergoing automated repairs by Google Cloud on the Turn SaaS platform. This is causing disruption across multiple numbers as services are being migrated from poorly performing server nodes to newly provisioned server nodes.
Resolved | Oct 18, 2023 | 12:07 GMT+02:00
All issues have been resolved and Turn is working as expected.
Resolved | Oct 04, 2023 | 12:48 GMT+02:00
The issue is been resolved.
Open | Oct 04, 2023 | 11:04 GMT+02:00
One of the servers in the pool of available servers is misbehaving and is automatically being replaced, causing restarts of various services in Turn. These restarts can cause message delivery delays and disconnects in the user interface. It is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are unaffected.
We are working to resolve the issue as quickly as possible.
Resolved | Oct 02, 2023 | 10:49 GMT+02:00
This issue has been resolved.
Monitoring | Sep 30, 2023 | 09:00 GMT+02:00
All services are back up and running again. We are continuing to observe the system.
Identified | Sep 30, 2023 | 08:38 GMT+02:00
The Google supplied managed database layer has not applied a configuration change relating to the allowed number of maximum active connections. We're applying it again impacted services are restarting.
Open | Sep 30, 2023 | 08:07 GMT+02:00
We're observing regular disconnections of the WhatsApp Business API infrastructure from the primary database. This will mean disconnections and interruptions for messaging of services using the WhatsApp Business API on https://whatsapp.turn.io .
Private clouds and dedicated clusters are unaffected.
We are investigating to root cause and will provide more information as it becomes available.
Resolved | Sep 27, 2023 | 13:10 GMT+02:00
All issues have been resolved and the application works as expected.
Open | Sep 27, 2023 | 11:37 GMT+02:00
We are encountering a major breakdown that impacts all services & APIs
Our engineers are working on it. We will update the progress shortly.
Resolved | Jul 26, 2023 | 12:47 GMT+02:00
The issue has been resolved and we will continue to monitor the situation.
Open | Jul 26, 2023 | 09:33 GMT+02:00
Automations are suffering from degraded performance. This is causing the delayed responses for many users. We are working to resolve the issue. There might a downtime of around 15 mins at 7:40 am UTC.
Resolved | Jul 25, 2023 | 17:48 GMT+02:00
The issue related to delayed responses is resolved.
Investigating | Jul 25, 2023 | 13:31 GMT+02:00
We have identified an issue that is causing the delay in automated responses. This impacts all clients in Turn shared cluster.
We are investigating the issue.
Resolved | Jun 26, 2023 | 16:17 GMT+02:00
All issues have been resolved.
Resolution in progress | Jun 26, 2023 | 15:51 GMT+02:00
Conversations are loading. We are addressing an issue with automations not working.
Resolved | Jun 26, 2023 | 15:39 GMT+02:00
The conversation loading issue has been resolved.
Open | Jun 26, 2023 | 15:18 GMT+02:00
We have identified an issue on the shared Turn cluster resulting in the conversation page not loading. The issue is not impacting private cloud customers.
We are working to resolve the issue as quickly as possible.
Resolved | May 16, 2023 | 14:01 GMT+02:00
The issue is resolved.
Open | May 16, 2023 | 10:10 GMT+02:00
We have observed an issue with execution of automated flows in Turn. This impacts all clients on Turn shared cluster.
We are working to resolve it as soon as possible.
Resolved | Apr 25, 2023 | 11:46 GMT+02:00
Turn interface is now loading for all clients. The underlying issue is resolved.
Investigating | Apr 25, 2023 | 09:37 GMT+02:00
The turn interface is loading for most of the clients. However, we still some disruptions. We are working to get it resolved as soon as possible.
Open | Apr 25, 2023 | 08:01 GMT+02:00
We have identified an issue due to which the Turn interface is not loading.
The above issue is impacting all customers on our shared cluster https://whatsapp.turn.io and private clusters.
We are working to resolve the issue as quickly as possible.
Resolved | Apr 07, 2023 | 10:47 GMT+02:00
This issue has been resolved.
Monitoring | Apr 06, 2023 | 20:20 GMT+02:00
All services are working normally, we're continuing to observe it.
Monitoring | Apr 06, 2023 | 16:58 GMT+02:00
All services are back online. Automated responses may still be delayed at times as message queues are being cleared.
We continue to monitor the situation.
Resolution in progress | Apr 06, 2023 | 14:57 GMT+02:00
The faulty servers have been taken out of rotation and have been replaced with new and health ones. Services are coming back online one by one.
Our apologies for this unplanned interruption of service on the Turn SaaS platform.
Identified | Apr 06, 2023 | 14:06 GMT+02:00
We have noticed that our cloud hosting provider has marked a number of machines in our production cluster as unhealthy and has proceeded to restart and replace them.
While services are restarting and migrating to new servers, there will be disconnects and WhatsApp services will be unavailable at times.
We are working on making sure this process completes as fast as possible.
Any messages received from users during this period will be processed as soon as services come back online.
Resolved | Mar 21, 2023 | 13:31 GMT+01:00
This issue has been resolved.
Monitoring | Mar 21, 2023 | 13:11 GMT+01:00
The issue has been resolved. An underlying piece of hardware had failed and all impact services were automatically migrated and restarted on a new server instance. Apologies for the inconvenience.
Open | Mar 21, 2023 | 12:49 GMT+01:00
We're noticing that services on our Turn SaaS services are being restarted by our cloud hosting environment. We are busy investigating what the underlying cause is.
This is causing message delivery delays and user interface connection errors.
Resolved | Feb 23, 2023 | 14:40 GMT+01:00
Issue is resolved. Collection updates again as expected every 5mins.
Open | Feb 22, 2023 | 15:11 GMT+01:00
We have identified an issue with Collection counts not updating. This means that the chat/message list in the Conversation view may have more or less chats/messages than you are seeing on the Dashboard view.
The above issue is impacting all customers, both on the shared cluster and on private clouds.
We are working to resolve the issue as quickly as possible.
Resolved | Feb 22, 2023 | 15:06 GMT+01:00
Duplicate reminders issue has been resolved.
Monitoring | Feb 06, 2023 | 12:37 GMT+01:00
We have shipped a fix for the duplicate message delivery observed in Reminders, and will continue to monitor it closely. The feature can be used again as usual.
Open | Feb 03, 2023 | 08:02 GMT+01:00
We are experiencing issues with Reminders resulting in multiple messages being sent to contacts. This could impact quality ratings and we therefore recommend to not use Reminders until the issue is resolved.
The above issue is impacting all customers on our shared cluster at as well as private cloud customers.
We are actively working to resolve it.
Resolved | Jan 06, 2023 | 12:01 GMT+01:00
The issue related to stacks with buttons and list is resolved.
Open | Jan 06, 2023 | 10:56 GMT+01:00
We have identified an issue with Stacks. The stacks that have button cards and emojis in the list items either fails to send an intended response or no response at all.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io.
We are working to resolve the issue as quickly as possible.
Resolved | Oct 25, 2022 | 13:43 GMT+02:00
WhatsApp reported message sending and receiving has been restored.
Open | Oct 25, 2022 | 10:21 GMT+02:00
WhatsApp reported major disruptions impacting the ability to send messages via the WhatsApp Business Platform. Their teams are working to mitigate the issue.
Resolved | Oct 14, 2022 | 17:14 GMT+02:00
This issue has been resolved, the backlog on the low priority queue has been cleared.
Open | Oct 14, 2022 | 17:02 GMT+02:00
Turn operates 3 levels of queue priority, low, default, and high. The low priority queue is drained with least urgency and the high priority queue is given maximum amount of resources to ensure fast delivery.
Which queues your events are dispatched to depends on how fast your endpoint responds. The response time of your endpoints are sampled once every 20 webhook event deliveries. The time it takes you to accept a message for delivery determines what queue the following event is going to be dispatched to. Please read https://whatsapp.turn.io/docs/api/settings#application-settings for the details and the response time based prioritisation.
For the past few hours there has been a steady build-up on our low-priority webhook delivery queue due to clients' webhooks failing to be delivered as a result of an AWS outage in India. We've allocated extra resources to the low priority queue to get its backlog to clear.
The default and high priority queues are not seeing any queue build up.
We will update here when it's completed.
Resolved | Aug 12, 2022 | 14:40 GMT+02:00
The issue has been resolved and media files work as expected again.
Open | Aug 12, 2022 | 14:26 GMT+02:00
We have identified an issue with sending and receiving media files.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
We are working to resolve the issue as quickly as possible.
Resolved | Aug 11, 2022 | 14:15 GMT+02:00
No further message delivery delays have been observed, this issue is resolved.
Monitoring | Aug 11, 2022 | 12:49 GMT+02:00
The rate limiting issue has been addressed and messages are now being delivered. We are continuing to monitor the situation.
Open | Aug 11, 2022 | 12:45 GMT+02:00
We have identified an issue with rate limiting on the Turn API affecting message delivery.
The above issue is impacting all customers on our shared cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
We are working to resolve the issue as quickly as possible.
Resolved | Jul 28, 2022 | 11:37 GMT+02:00
The issue has been resolved.
Open | Jul 28, 2022 | 11:01 GMT+02:00
We have identified an issue with multiple automated responses being send. We are working to resolve the issue as quickly as possible.
The above issue is impacting all customers on the shared Turn cluster at https://whatsapp.turn.io. Private cloud customers are not affected.
Resolved | Jul 12, 2022 | 14:16 GMT+02:00
We have resolved the issue that was causing delay in appearance of messages in chat list and search results.
Open | Jul 12, 2022 | 13:12 GMT+02:00
We have identified an issue due to which the messages appear in the chat list and in the search result with a delay. This is impacting all clients.
We are working to resolve the issue.
Resolved | Jul 02, 2022 | 05:23 GMT+02:00
The issue around automation is resolved for all clients.
Open | Jul 01, 2022 | 08:03 GMT+02:00
We have identified an issue with automations. Adding a new automation from turn interface returns a black screen. This is impacting all clients including the clients on private clusters.
We are working to resolve it.
Resolved | Jun 14, 2022 | 17:13 GMT+02:00
The issue related to media messages delivery is resolved for all numbers. All systems are working as expected.
Open | Jun 14, 2022 | 16:48 GMT+02:00
We have observed that the media messages are not sent or received from all numbers on Turn shared cluster. We are investigating the issue. We hope to resolve it shortly.
Resolved | Jun 14, 2022 | 15:57 GMT+02:00
The issue related to message delivery is resolved fully.
Monitoring | Jun 14, 2022 | 11:45 GMT+02:00
The issue related to message delivery is resolved and we are monitoring our systems.
Resolved | Jun 04, 2022 | 09:27 GMT+02:00
The cause for message processing delay has been identified and rectified. This incident did not affect all numbers, however those numbers affected would have seen intermittent delays in message processing. Normal operation has been restored.
Investigating | Jun 04, 2022 | 06:36 GMT+02:00
We have identified further delays in message processing, Turn engineers are investigating.
Resolved | Jun 04, 2022 | 05:08 GMT+02:00
Whilst some additional message processing delay was observed whilst monitoring, no delays are currently being observed.
Monitoring | Jun 04, 2022 | 03:01 GMT+02:00
The cause for message processing delay has been identified and rectified. We are continuing to monitor the situation.
Open | Jun 04, 2022 | 02:15 GMT+02:00
There's currently a delay in messages being processed, Turn engineers are investigating.
Resolved | May 25, 2022 | 22:07 GMT+02:00
No further message processing delay has been observed, the issues has been resolved.
Monitoring | May 25, 2022 | 20:18 GMT+02:00
The cause for message processing delay has been identified and rectified. Only a select number of numbers were affected. We are continuing to monitor the situation.
Open | May 25, 2022 | 19:45 GMT+02:00
There's currently a delay in messages being processed, Turn engineers are investigating.
Resolved | May 03, 2022 | 19:06 GMT+02:00
The maintenance window has closed and all messages queued have been processed.
Open | May 03, 2022 | 18:11 GMT+02:00
There's currently a delay in messages being processed for search results due to an active maintenance window. We expect this to be resolved within an hour. All messages are queued and will be processed once the maintenance is done.
Your services are online and function, there's only a delay in some messages being visible in the chat list or the search results page.
Resolved | Apr 25, 2022 | 12:51 GMT+02:00
The new version has been released successfully.
Open | Apr 21, 2022 | 16:01 GMT+02:00
We are pausing message indexing for a few minutes as part of our current release. During this time there will be a delay for messages to appear in the Turn UI. Message sending and receiving will not be impacted.
This will affect customers on app.turn.io around 16:00 GMT+2. Private Cloud customers will not be impacted.
Resolved | Apr 19, 2022 | 11:50 GMT+02:00
The new version has been released successfully.
Open | Apr 19, 2022 | 11:20 GMT+02:00
Customers on app.turn.io might experience brief downtime at around 11:20am GMT+2 as a result of our current release. Private Cloud customers will not be impacted.
Resolved | Mar 30, 2022 | 06:50 GMT+02:00
The issue related to the message delivery is resolved for all clients.
Open | Mar 24, 2022 | 07:06 GMT+01:00
There is an issue identified by WhatsApp team at their own end that is impacting all clients on WhatsApp business platform.
Businesses running v2.39.1 and v2.39.2 of the On-Premises API are unable to respond to a customer-initiated conversation more than 7 days after the conversation was initiated. WhatsApp team is currently investigating the root cause and proposing a mitigation.
We are monitoring the communications from WhatsApp team.
Resolved | Mar 24, 2022 | 06:27 GMT+01:00
The issue around thread is now resolved.
Open | Mar 24, 2022 | 06:27 GMT+01:00
The issue around threads is now resolved.
Open | Mar 14, 2022 | 11:53 GMT+01:00
We have identified an issue with the threads with reply buttons. The threads fails to load or the questions cards inside the threads are missing. In some cases the threads fails to save.
The above issue is impacting few clients on our shared cluster at https://whatsapp.turn.io
We are working to resolve the issue.
Resolved | Mar 11, 2022 | 02:30 GMT+01:00
Further monitoring reveals no further delays in message receipt and delivery. This issue has therefore been resolved.
Monitoring | Mar 11, 2022 | 01:39 GMT+01:00
The cause of the delay has been identified and rectified. All numbers should be operational again. Turn engineers are continuing to monitor the situation.
Open | Mar 11, 2022 | 01:04 GMT+01:00
A delay in message receipt and delivery has been observed on certain numbers. Turn engineers are investigating.
Resolved | Feb 22, 2022 | 13:03 GMT+01:00
The issue related to message delivery is resolved for all clients.
Monitoring | Feb 22, 2022 | 13:00 GMT+01:00
On 19 February 2022 from 11:15 to 16:45 UTC and again on 21 February 2022 from 08:15 to 12:45 UTC message delivery was disrupted for a limited set of WhatsApp numbers hosted by Turn. During this time affected numbers would be unresponsive or slow to receive and process messages.
What caused it?
We will use a simple comparison to explain the incident for our non-technical users, and then elaborate with all the technical details.
Let's say we have a bus with WhatsApp numbers on Turn as passengers on the bus, and each passenger brought a lot of luggage with them. The luggage represents each service starting up to be able to send and receive messages. The bus broke down and another bus was called in immediately to transfer the passengers to, but the passengers had so much luggage that it took some time to do the transfer. During the time it took to do the transfer service interruption was experienced.Now let’s explain it in detail.
Turn hosts WhatsApp numbers on a collection of clustered virtual machines. These virtual machines need to be replaced as part of general maintenance or upgraded from time to time. The process of replacing virtual machines involves creating new virtual machines followed by moving workloads from the existing machines to the new machines. Moving workloads involves first stopping a workload on an existing virtual machine, then starting it again on a new machine.
In the general case this process of moving a workload from one virtual machine to another should not result in noticeable service disruption as stopping and starting of any given workload should complete within 30 seconds. However, during startup some but not all workloads can cause a spike in CPU usage. This can lead to CPU contention and a delay in process readiness if a large number of workloads exhibiting this behavior are started at the same time.
The incident on 19 February was triggered by an automated process replacing a number of virtual machines in Turn's hosting environment. However in this case the workloads on the virtual machines being replaced were inadequately distributed on the virtual machines being replaced in such a way that the majority of them would exhibit a large spike in CPU usage during startup. This led to CPU contention as the virtual machines were replaced and a large number of expensive processes restarted simultaneously, leading to significant delays in workloads being ready to process messages.
The incident on 21 February was caused in a similar fashion by CPU contention, however in this case it was triggered by rollout of configuration changes to the Turn hosting environment meant to address some of the problems encountered on the 19th. Specifically, workloads were redistributed more equally across all virtual machines in the hosting environment. However, even with more balanced workloads, CPU contention was still observed on some virtual machines during process startup, again resulting in significant delays in workloads being ready to process messages.
What are we doing about it?
To address this incident the following fixes having been released:
- Paused the automatic GCP upgrade schedule until we reduce the process startup times. Automatic GCP maintenance can still happen and cause disruption, so our key focus is on reducing process startup times.
- Rebalance workloads over virtual machines to reduce potential for CPU contention during workload startup.
Work is still ongoing on the following fixes:
- Optimize workloads to eliminate CPU usage spikes during startup and thus the potential for CPU contention.
- Reconfigure Turn hosting environment to be more conservative in terms of allowing workload disruption. This means that in the case of virtual machines being replaced that only a small number of workloads will be moved at a time to ensure that even if CPU spikes were to occur during startup, that they would not lead to CPU contention.
- Clearly schedule maintenance windows on Turn’s status page to surface potential for disruption.
Resolved | Feb 03, 2022 | 09:06 GMT+01:00
Upgrades are successfully done. All systems are working as expected.
Resolution in progress | Feb 02, 2022 | 14:30 GMT+01:00
The automatic upgrades of underlying infrastructure is in progress. This is the reason why messages are failing to deliver. We are monitoring and working to resolve the issue.
Open | Feb 02, 2022 | 12:58 GMT+01:00
We have observed some issues with messages delivery and receipt. This is impacting few clients on app.turn.io. We are working to resolve the issue.
Resolved | Jan 27, 2022 | 14:17 GMT+01:00
The issue around the automation page in Sandbox accounts is resolved for all accounts.
Open | Jan 26, 2022 | 15:03 GMT+01:00
We have identified that the automation page in the sandbox accounts is not loading.
This impacts all sandbox accounts only.
We are working to resolve the issue as soon as possible.
Resolved | Nov 16, 2021 | 19:48 GMT+01:00
Turn application and messaging service operation has now been restored.
Monitoring | Nov 16, 2021 | 19:20 GMT+01:00
Turn application and messaging services are now accessible but might still have degraded performance.
We are continuing to monitor the situation as Google continues to address a Cloud Networking outage.
Open | Nov 16, 2021 | 19:05 GMT+01:00
The load balancing service used to serve the Turn application and messaging services is currently experiencing a major outage. As a result Turn is unable to process messages at this time.
We are continuing to monitor the situation.
Resolved | Nov 05, 2021 | 13:07 GMT+01:00
Upgrades are completed. All systems are working as expected.
Open | Nov 05, 2021 | 11:44 GMT+01:00
The underlying hosting infrastructure is undergoing an automated upgrade. All of the servers behind https://app.turn.io is being upgraded sequentially, services may experience message delivery delays or login issues while the upgrade is applied.
Resolved | Nov 02, 2021 | 11:41 GMT+01:00
The upgrades are completed. All systems are working as expected.
Open | Oct 28, 2021 | 10:11 GMT+02:00
The underlying hosting infrastructure is undergoing an automated upgrade. All of the servers behind https://app.turn.io is being upgraded sequentially, services may experience message delivery delays or login issues while the upgrade is applied.
Resolved | Oct 21, 2021 | 09:59 GMT+02:00
The issue has been resolved.
Open | Oct 21, 2021 | 09:15 GMT+02:00
We have observed an issue with the Turn user interface not loading correctly or loading slowly. This is impacting some of our clients. Our team is working on the issue. We hope to resolve it soon.
Resolved | Oct 08, 2021 | 23:55 GMT+02:00
The upgrades have completed.
Open | Oct 08, 2021 | 22:40 GMT+02:00
The underlying hosting infrastructure is undergoing an automated upgrade. Each of the servers behind https://app.turn.io is being upgraded sequentially, services may experience message delivery delays while the upgrade is applied.
Resolved | Oct 05, 2021 | 06:35 GMT+02:00
This has been resolved by WhatsApp.
Open | Oct 04, 2021 | 18:39 GMT+02:00
Due to the global WhatsApp network being offline, Turn is unable to process messages.
Resolved | Oct 04, 2021 | 18:38 GMT+02:00
This has been resolved.
Monitoring | Sep 20, 2021 | 06:04 GMT+02:00
Message delivery delays have been resolved. The underlying cause was a queue server running out of disk space. We're continuing to attend to this problem to prevent a repeat.
Open | Sep 20, 2021 | 05:42 GMT+02:00
We're seeing a message queue buildup and some delivery delays on app.turn.io. We are attending to the issue and will provide updates here as we work towards fixing the problem.
Resolved | Sep 16, 2021 | 22:02 GMT+02:00
The optimisations have been applied, any pending messages have been processed.
Open | Sep 16, 2021 | 21:44 GMT+02:00
We are applying some database and infrastructure optimisations, these are causing some message delivery delays. All pending messages will be processed within a few minutes.
Resolved | Sep 14, 2021 | 18:58 GMT+02:00
This issue has been resolved as part of our latest deploy.
Open | Sep 08, 2021 | 15:59 GMT+02:00
We're experiencing an issue with pagination when you view a conversation from the Search page. Currently the new messages overwrites the first ones instead of getting appended which is why some of the messages are not visible in the Turn interface.
No messages are lost due to above issue. We are working on a fix. We hope to resolve it as soon as possible.
Resolved | Sep 14, 2021 | 18:15 GMT+02:00
This issue has been resolved. It was due to the deploy of a new release taking significantly longer than expected.
Open | Sep 14, 2021 | 15:54 GMT+02:00
We are experiencing an issue with automation on Turn and are working to get it resolved as quickly as possible. We'll provide updates here as we continue to investigate.
Resolved | Jul 22, 2021 | 12:54 GMT+02:00
We have resolved the issue of button automation. All features are working as expected for all clients.
Identified | Jul 22, 2021 | 10:40 GMT+02:00
We have identified an issue with the button automation. When users click on the button inside message templates that they have received then they either get a catch all message or no message at all from the service.
This is impacting all clients. We are working hard to get it resolved.
Resolved | Jul 04, 2021 | 00:02 GMT+02:00
The upgrades have completed and everything's been operating normally since 19:20 UTC.
Open | Jul 03, 2021 | 20:49 GMT+02:00
Due to an unannounced service upgrade, the cluster powering app.turn.io was restarted. This may cause some intermittent interruptions in messaging and delays in messages being available in search.
We'll update this status update once completed.
Resolved | Jun 25, 2021 | 14:08 GMT+02:00
The issue related to threads is now resolved. All features are working as expected.
Open | Jun 25, 2021 | 10:58 GMT+02:00
We have found an issue that is affecting threads feature. This is impacting some of the clients on app.turn.io. Issues such as saving threads and updating threads is associated with it. We are working tirelessly to get it resolved as quickly as possible.
Resolved | Jun 21, 2021 | 12:00 GMT+02:00
We have resolved the issue related to threads page. Threads page is working as expected for all clients.
Open | Jun 21, 2021 | 09:54 GMT+02:00
We have identified an issue with the Threads automation page. Threads page is giving a white screen and is failing to load. This is impacting all clients.
Our teams are working on the issue. We hope to resolve it soon.
Resolved | May 13, 2021 | 19:13 GMT+02:00
The issue of sending media messages and templated messages with button is now resolved. All systems are working as expected.
Monitoring | May 13, 2021 | 12:10 GMT+02:00
The issue persists at WhatsApp's end. Messages templates with Buttons and Media messages are impacted due to this outage. We are closely following the updates from WhatsApp.
Resolved | Apr 01, 2021 | 13:32 GMT+02:00
The issue pertaining to loading of conversations is now resolved. All features are working as expected.
Open | Apr 01, 2021 | 12:51 GMT+02:00
We have encountered an error at our end due to which either turn is not loading or the collections/automations are not available. This is impacting all clients on app.turn.io. It is not impacting private clouds.
Our engineers are working to get it resolved as soon as possible.
Resolved | Mar 22, 2021 | 02:21 GMT+01:00
Content distribution network outage ended. All systems are working as expected.
Open | Mar 19, 2021 | 09:04 GMT+01:00
The content distribution network that is used to serve the Turn frontend application is currently experiencing a major outage. This outage might impact some of our clients.
Some of our clients might not be able to load the turn application. We are monitoring the situation.
Resolved | Mar 16, 2021 | 12:09 GMT+01:00
Clients on Infobip can now send and receive messages. The issue is resolved now.
Open | Mar 16, 2021 | 08:33 GMT+01:00
We have observed that the message delivery for clients on Infobip BSP fails. This is happening for all inbound and outbound messages. The issue is impacting only those clients who are on Infobip.
We are working to resolve the issue as soon as possible.
Resolved | Mar 04, 2021 | 06:39 GMT+01:00
We have upgraded our search infrastructure and message history is now available for 12 months.
Resolution in progress | Feb 22, 2021 | 07:08 GMT+01:00
We have restored the chat history for past 12 months for all app.turn.io clients. The backfill for private cloud clients are now in progress and should be completed in the next 2 days. We have also upgraded our search infrastructure. This means that the time taken for execution of search query is reduced. This also means that the performance of loading conversations, receiving and sending messages is also improved.
Resolution in progress | Feb 17, 2021 | 12:38 GMT+01:00
We have started the process to restore your full message history. As a result, search results and totals shown in Collections may vary more than expected. We will update you once the history is fully restored.
Resolution in progress | Feb 11, 2021 | 09:11 GMT+01:00
We're performing a system upgrade in response to performance issues with our search infrastructure. This will temporarily limit Search history to active users to the last 6 weeks for all our clients. As a result, the totals shown in Collections will only reflect users who have interacted with your service since 18 December 2020. No other features will be impacted except for Collections and Search.
To can learn more visit:
https://learn.turn.io/product-updates/10-february-2021-temporary-search-limitations-while-we-do-a-search-feature-upgrade
Resolved | Feb 24, 2021 | 16:08 GMT+01:00
All automations are now available.
Open | Feb 23, 2021 | 16:30 GMT+01:00
We have found an issue in our system which is causing availability of only 50 automation rules. All the rules that are not available are working fine for the users but those rules are not visible.
This is impacting all clients including clients on private clouds.
We are working to get it resolved soon.
Resolved | Feb 04, 2021 | 11:06 GMT+01:00
We have deployed a fix for this issue. The changes that we have done in our infrastructure have not only solved the loading conversations/chat issue but also reduce the time of loading chats.
Chats/conversations should now be working properly for all clients including clients on private clouds.
Resolved | Jan 29, 2021 | 11:00 GMT+01:00
Conversation are loading for all clients now.
Monitoring | Jan 26, 2021 | 11:47 GMT+01:00
We have applied a fix for the issues of loading conversation and display of chats on dashboard. All clients can now have a smooth loading of their conversations and should now have all the chats displayed in their dashboards.
We are, however, keeping this issue under monitoring.
Open | Jan 25, 2021 | 14:27 GMT+01:00
The issues of loading conversation and availability of chats in dashboard are now impacting all clients including clients on private clouds.
Our engineering teams are constantly working on a fix.
Resolution in progress | Jan 25, 2021 | 12:49 GMT+01:00
We are making progress on the issue of loading conversations. Currently, conversations are loading fine for all clients.
There is however a related issue of availability of new chats in the dashboard. New Chats are not reflected in the client's dashboard. This is affecting all clients on app.turn.io.
We are as eager as you are to solve the issue and we are working tirelessly to achieve that.
Open | Jan 25, 2021 | 09:46 GMT+01:00
Issue of loading collections still persists for all the clients on app.turn.io. We are working on it to get it resolved.
Resolution in progress | Jan 22, 2021 | 08:54 GMT+01:00
We have applied some changes to improve the performance. We are keeping it under watch and working on a fix.
Open | Jan 20, 2021 | 07:01 GMT+01:00
Conversations fails to load currently. This issue is affecting most of the clients on app.turn.io . This issue is not affecting the clients with private clouds. We are working hard to resolve it.
Resolution in progress | Jan 19, 2021 | 06:28 GMT+01:00
Collections are now loading but we are experiencing a degraded performance. It is taking more time than usual to load collection. We are working hard to get it resolved.
Monitoring | Jan 18, 2021 | 12:48 GMT+01:00
We have corrected our systems and now the conversations are loading properly. We are monitoring our system for next few hours.
Open | Jan 18, 2021 | 08:01 GMT+01:00
We have found an issue with app.turn.io which is primarily affecting loading of conversations in most of the whatsapp Bot lines.
We are working hard to get it resolved as quickly as possible.
Resolved | Jan 05, 2021 | 17:24 GMT+01:00
We've been observing this issue over the holidays and it is now resolved.
Open | Dec 23, 2020 | 12:32 GMT+01:00
If you continue to have problems logging and get an error about an "invalid token" please delete the browser cookies for https://app.turn.ioa and https://whatsapp.turn.io and refresh
Open | Dec 23, 2020 | 11:06 GMT+01:00
We've applied some extra security policy's to Turn. If you are finding yourself unable to connect, or disconnected, you need to logout and log back in again.
Resolved | Dec 23, 2020 | 12:50 GMT+01:00
This issue is now resolved.
We've identified the root cause to relate to big query synchronisation for a number of clients experiencing above average messaging throughputs. We've disabled the big query synchronisation for one account and are working on a permanent fix.
Open | Dec 23, 2020 | 12:31 GMT+01:00
We're experiencing some interruptions with message delivery. We are investigating the root cause.
Resolved | Dec 22, 2020 | 11:22 GMT+01:00
The issue was resolved, all backlogged messages that were still waiting to be made available in the search and collections results have been processed.
Open | Dec 21, 2020 | 14:12 GMT+01:00
We're seeing a backlog build up on our search infrastructure. This can result in a delay in messages and chats becoming visible in collections. We're working on resolving this.
Messaging is unaffected by this.
Resolved | Dec 18, 2020 | 15:56 GMT+01:00
The issue has been resolved.
Investigating | Dec 18, 2020 | 11:09 GMT+01:00
While messages are being processed as normal, they may not be showing up in search results or in the chat list yet.
We are continuing to investigate the issues with the search infrastructure and will update here as soon as we know more.
Open | Dec 18, 2020 | 10:26 GMT+01:00
We're experiencing down time due to problems with indexing of messages on our search infrastructure.
We're investigation and will update as soon as we know more.
Resolved | Dec 14, 2020 | 15:21 GMT+01:00
Google seems to have resolved most of their issues.
Open | Dec 14, 2020 | 13:13 GMT+01:00
Google is having a global outage and Turn relies on Google for login and account management.
While Google is having these problems, you may face issues while logging into any Turn instance.
Resolved | Nov 27, 2020 | 15:23 GMT+01:00
The issue has been resolved.
Open | Nov 27, 2020 | 11:42 GMT+01:00
We've found an issue with automations that is impacting numbers who have more than 50 pieces of content loaded in Turn. We're busy addressing this issue.
Resolved | Nov 10, 2020 | 16:42 GMT+01:00
The issue has been resolved for all Turn installations.
Monitoring | Nov 10, 2020 | 13:11 GMT+01:00
The issue is resolved on app.turn.io, we're monitoring the situation on the private cloud installations.
Resolved | Oct 21, 2020 | 14:13 GMT+02:00
The issue has been resolved for the 2 clusters impacted. The underlying technical root cause was a database migration causing a table lock on one of the applications' main tables. This was further complicated by automated database cleanup processes happening on the same table a the same time.
Our apologies for the downtime experienced.
Investigating | Oct 21, 2020 | 12:44 GMT+02:00
The fix we've applied has not yet had it's intended effect. We're continuing to investigate.
Resolution in progress | Oct 21, 2020 | 11:49 GMT+02:00
A fix is being released to the production environments impacted.
Open | Oct 21, 2020 | 11:17 GMT+02:00
Unfortunately we pushed a faulty release to 2 of our production clusters. This is causing downtime for https://app.turn.io. We are busy issuing a fix and the systems should be online again shortly.
Our sincere apologies for this inconvenience, we will provide updates here as we address the underlying issue.
Resolved | Oct 08, 2020 | 14:07 GMT+02:00
The issue has been resolved.
Open | Oct 08, 2020 | 13:03 GMT+02:00
We've found an issue where Turn is not accepting status updates on messages. This can mean that you'll experience a delay in seeing your messages marked as read, sent, or delivered. We're busy addressing this issue.
Resolved | Sep 15, 2020 | 10:47 GMT+02:00
All system upgrades have been applied.
Open | Sep 15, 2020 | 10:14 GMT+02:00
We're performing a system upgrade in response to Google's https://cloud.google.com/kubernetes-engine/docs/security-bulletins#gcp-2020-012 security bulletin on all our Google Cloud Platform hosted systems. This will involve various restarts across the platforms. Any messages received during a restart will be handled immediately as the restarts of the various components are completed.
Resolved | Sep 15, 2020 | 10:07 GMT+02:00
We've observed this for a few days and it is now resolved.
Monitoring | Sep 11, 2020 | 13:38 GMT+02:00
We've put some more fixes in places and are observing the system's behaviour. This issue seems to be related to automatic upgrades performed by the hosting services that app.turn.io is using. This is not impacting any of the private cloud setups.
Investigating | Sep 11, 2020 | 12:01 GMT+02:00
The fix we put in place is no longer resolving this issue we are experiencing with database connections. We're investigating.
Resolved | Sep 11, 2020 | 10:43 GMT+02:00
The issue is resolved. We're continuing to monitor the systems.
Open | Sep 11, 2020 | 10:31 GMT+02:00
We've found an issue with a number of numbers unable to receive messages from WhatsApp. We've identified the issue and are busy addressing it.
Any messages currently pending delivery will be processed shortly.
Resolved | Aug 25, 2020 | 09:23 GMT+02:00
Collection search indexing has been optimised to reduce load on the search backend. Search query and collection performance has been greatly improved as a result.
We're continuing to work on improvements to prevent this happening in future - in particular we're changing the way All Conversations is architected so that it is much faster and doesn't rely on search
Monitoring | Aug 25, 2020 | 09:22 GMT+02:00
Collection search indexing has been optimised to reduce load on the search backend. Search query and collection performance has been greatly improved as a result.
We're continuing to work on ways to prevent this occurring in future including changing the way All Conversations is architected so that it is much faster and doesn't rely on search.
Resolution in progress | Aug 19, 2020 | 14:35 GMT+02:00
To alleviate some of the load we'll be temporarily be turning off the total user count display for collections.
Resolution in progress | Aug 19, 2020 | 13:39 GMT+02:00
Currently, Collections rely on Search functionality to find conversations that match the Collection criteria. The All Conversations Collection, in particular, puts a high load on Search, slowing down the performance across all other Collections.
We're busy working on a change to how the All Conversation Collection functions to ensure that is performs faster.
Investigating | Aug 18, 2020 | 12:42 GMT+02:00
Some users are experiencing issues where Collections are loading a blank screen, or partial screen.
We're exploring different reasons this may be happening.
Resolved | Aug 19, 2020 | 13:38 GMT+02:00
Content is now behaving as usual on app.turn.io
Resolution in progress | Aug 19, 2020 | 10:58 GMT+02:00
We found an issue where content is no longer editable due to a change we made in the underlying content format.
This has now been reverted. Please do a hard refresh to ensure you see the changes.
Resolved | Jul 31, 2020 | 17:25 GMT+02:00
A new release is being deployed to all the clusters, all inbound media for Infobip numbers will be working again as expected within a few minutes.
Resolution in progress | Jul 31, 2020 | 12:23 GMT+02:00
QA passed, we'll be releasing to all our production environments shortly.
Resolution in progress | Jul 31, 2020 | 10:55 GMT+02:00
We've identified the issue and have a fix in place. We're currently testing it in our QA environment.
Identified | Jul 31, 2020 | 10:28 GMT+02:00
This seems to be limited to numbers backed by Infobip. We're continuing to dig into this issue.
Open | Jul 31, 2020 | 09:03 GMT+02:00
We're seeing an issue where media received via WhatsApp is not displaying properly in the UI nor accessible via the API.
We are busy investigating and will provide updates as soon as possible.
Resolved | Jul 28, 2020 | 17:27 GMT+02:00
Issue is resolved
Closed | Jul 28, 2020 | 17:26 GMT+02:00
The issue has been resolved.
Resolution in progress | Jul 28, 2020 | 15:24 GMT+02:00
We've indentified one possible root cause which could result in processed messages being rescheduled for processing again by the automation system.
Resolution in progress | Jul 28, 2020 | 14:47 GMT+02:00
The backlog of background jobs has been processed and things should be snappy again. We're continuing to investigate the root cause of this issue.
Identified | Jul 28, 2020 | 14:37 GMT+02:00
We've identified a situation where a number is constantly rescheduling new jobs in the background job queue causing it to grow constantly.
Open | Jul 28, 2020 | 14:08 GMT+02:00
Due to a problematic release, there are quite a few messages pending to be processed and still due for delivery. We are working through the backlog and services relying on the automation system should be responsive again shortly.
Resolved | Jul 22, 2020 | 14:20 GMT+02:00
This issue is now resolved. Please get in touch with us if you are having issues with conversations or messages not being visible in the UI search results or collections.
Monitoring | Jul 22, 2020 | 13:41 GMT+02:00
Our search infrastructure upgrade has completed and we're processing a backlog of conversations and messages needing to be processed by the search backend. Once they've been processed they will show up in your search results and collections overviews. We're expecting this to be completed within the next hour.
Open | Jul 22, 2020 | 11:03 GMT+02:00
We've reprovisioned the search infrastructure and are re-indexing the chat histories for all clients. While this in progress clients may have an incomplete view of the chats in search results and collections.
Open | Jul 20, 2020 | 14:22 GMT+02:00
We're noticing we're hitting some infrastructure capacity limits on our app.turn.io hosting environment. We're busy adding more capacity to meet the demand.
Resolved | Jun 30, 2020 | 12:23 GMT+02:00
This issue has for now been resolved.
Monitoring | Jun 29, 2020 | 12:29 GMT+02:00
Services are operating as normal again. The search infrastructure is doing better but the underlying cause is not fully resolved yet. We're working on a more permanent solution.
Open | Jun 29, 2020 | 11:22 GMT+02:00
Our Elasticsearch installation is suffering from degraded performance. This is causing the UI to load slowly for many users. We are working on restoring service as soon as possible.
Messaging services should be operational as normal.
Resolved | Jun 10, 2020 | 12:06 GMT+02:00
This issue has been resolved.
Open | Jun 10, 2020 | 11:52 GMT+02:00
Due to a new software release, some messages are not being delivered to some countries.
A fix is being released and should be resolved shortly.
Resolved | May 30, 2020 | 13:26 GMT+02:00
We've updated how we route traffic to whatsapp.turn.io and the issue has been resolved by issuing a different SSL certificate.
Open | May 30, 2020 | 13:12 GMT+02:00
We have found an issue with an SSL certificate's authority certificate having expired which is causing some downtime for some clients.
We're working on resolving this.
Resolved | Feb 27, 2020 | 15:43 GMT+01:00
This issue has been resolved.
Resolution in progress | Feb 07, 2020 | 12:44 GMT+01:00
For clients with many collections spanning hundreds of thousands of monthly active users the Turn dashboard page was having trouble loading. We isolated the issue to collections taking longer to load than could reasonably be expected.
We are working on a fix to address this issue for these clients.
Resolved | Feb 26, 2020 | 12:21 GMT+01:00
This issue has been resolved.
Monitoring | Feb 24, 2020 | 13:29 GMT+01:00
We're investigating some issues reported with images not being delivered via Infobip.
Monitoring | Feb 12, 2020 | 08:48 GMT+01:00
We are continuing to monitor media attachment behaviour over the next few days.
Investigating | Jan 31, 2020 | 10:48 GMT+01:00
We have found an issue where attachments such as location pins and audio files are displaying incorrectly in the Turn UI.
The Turn team is working to get it resolved as quickly as possible.
Resolved | Feb 12, 2020 | 08:47 GMT+01:00
Faktory has been behaving as expected over the last 5 days and therefore this incident is considered resolved.
Monitoring | Feb 07, 2020 | 16:19 GMT+01:00
A temporary fix was put in place at 9:07 UTC. A permanent fix will be deployed shortly.
Monitoring | Feb 07, 2020 | 12:43 GMT+01:00
We have found an issue with Turn and are working tirelessly to get it resolved as quickly as possible.Turn off-loads the delivery of webhooks and indexing of messages and conversations to a background process. This allows Turn’s APIs and frontend to remain performant by delegating tasks that do not require immediate processing, or tasks which are allowed to take a little longer to complete, and to continue working in the background while Turn continues to focus on message processing.
This morning the piece of Turn infrastructure that is responsible for accepting and scheduling these tasks ran into its maximum allowance of disk space. As a result, it intermittently refused to accept more tasks as it briefly had no disk space to store them.
The impact on clients was that webhook deliveries were delayed and the search and conversation listings were at times showing outdated information.
We increased the disk space allocation for the background worker and we have reindexed all the messages and conversations for all clients to make sure the frontend is displaying the latest messages and updated conversations again.
We are putting measures in place to make sure the disk space allocations increase as our clients’ monthly active users and message volumes increase.