P0 - Disruption on our platform
Timeline · 1 update
- resolved Aug 26, 2026, 08:21 AM UTC
From 18:12 - 18:17 we encountered a global platform disruption.
iAdvize had 29 outages in the last 2 years totaling 47h 21m of downtime — averaging 1.2 incidents per month.
There were 29 iAdvize outages since September 2, 2024 totaling 47h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.
From 18:12 - 18:17 we encountered a global platform disruption.
We experienced disruptions on our platform impacting knowledge libraries are not accessible in the admin, and AISA / Conversation Starters are returning empty messages / no responses. From 1:40pm to 2:02pm
We experienced minor slowdowns starting at 11:00. From 11:40, there was a spike in errors: Agents were unable to log in to the desk, no conversations were received, and there were slowdowns on the admin side in particular. The issue has now been resolved, but we continue to monitor the situation. Thank you for your understanding.
We experienced a disruption affecting Copilot conversation processing (Duration: 11:05 - 11:25 (UTC) | 20 minutes) due to internal misconfiguration. The issue has been fully resolved. We apologize for any inconvenience and thank you for your patience.
We are currently experiencing an issue with the social channel. You will not be able to send or receive messages in social conversations. We are working on it.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Shopping Assistant experienced random disruptions between 2:40 PM and 3:00 PM (CET). Conversations were initiated by visitors, but the Shopping Assistant was not always able to respond systematically. The issue has been identified and fixed. Thank you for your understanding.
Our shopping assistant experienced random disruptions between 1:17pm and 1:48pm. Conversations were initiated by visitors, but the Shopping Assistant did not respond consistently. The issue has been identified and fixed. Thank you for your understanding.
We're currently experiencing some technical issues causing our Copilots to respond slowly. We are investigating.
We are continuing to investigate the issue.
Issue is now mitigated. Copilot is back to normal.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix is currently being published.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A deployment on Oct 27, 2025 3:21 PM intended to extend Admin session duration to 1 hour unintentionally reduced Desk agent session duration from 1 day to 1 hour. So, Desk agents were forced to re-authenticate hourly until the fix was deployed on Oct 28, 2025 1:57 PM. Sorry for the commotion.
The copilot feature is facing issues. Message processing is significantly slower. The ingestion and processing of knowledge bases feeding the copilots is also significantly slowed down. We suspect a network failure at our LLM provider.
The issue is identified: Looks like we are facing connexion issues between iAdvize and our LLM provider. We are investigating further.
We are looking for alternatives to restore the platform to normal operation as quickly as possible.
We are continuing to investigate this issue.
We have implemented a solution to mitigate the problem. We are monitoring Copilot.
As we are not seeing any improvement, we are trying to implement another solution to mitigate the issue.
The latest correction has been successfully completed. Copilot is back and working as expected.
This incident has been resolved.
We are currently experiencing disruptions on our platform affecting its proper functioning. It is difficult to respond to visitors and to close conversations from Social channels.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues on social channels.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently facing an issue. The creation of conversations is impacted
The issue has been identified, and a fix is currently being deployed.
A fix has been implemented. We are monitoring the solution.
This incident has been resolved.
We are currently facing an issue. The creation of conversations is impacted Handling conversations in the Desk might be impacted too
The issue has been identified, and a fix is currently being deployed.
A fix has been implemented. We are monitoring the solution.
On 07/09 (07:01–07:18 CET) and 08/09 (09:37–09:55 CET), the iAdvize platform experienced instability due to issues with our networking service. 07/09: The platform (Admin, Desk, Livechat) was unavailable. Services were restored after a restart. 08/09: Livechat and Desk were unstable. Admin remained operational. Services were restored after a system reboot. Everything is now fully operational. We are reinforcing our systems to avoid a recurrence. We sincerely apologize for the inconvenience caused.
Between August 19th 16:48 and August 20th 10:45, we experienced a disruption that affected the availability of certain Bots (Copilot + Workflow). Due to a technical issue in the synchronization process, certain Bots were incorrectly shown as unavailable. This impacted only a subset of our clients, where some engagement notifications were not displayed, and conversation creation was reduced. The issue was resolved on August 20th at 10:45 by restarting the impacted services. We are adding automated monitoring and restart mechanisms to prevent this from happening again and to ensure faster recovery in case of future incidents. We sincerely apologize for the inconvenience caused, and thank you for your understanding.
We are currently facing an issue. Notification won't display on websites
We are continuing to investigate this issue.
The issue has been identified and a fix is deployed.
The issue is resolved. We are monitoring the whole solution.
The latest patch is released. We are monitoring the solution.
The issue is resolved.
We are having a production issue right now, the bots are not able to reply to visitors and conversation report is not displaying conversations, we are currently investigating the cause
We found the root cause of the issue. Yet, a fix is live. All is working normally. We keep monitoring the production.
This incident has been resolved.
We are having a production issue right now, the bots are not able to reply to visitors and conversation report is not displaying conversations, we are currently investigating the cause
We found the root cause of the issue. Yet, a fix is live. All is working normally. We keep monitoring the production.
This incident has been resolved.
We are facing an issue related to the stats. Some of them won't update for now. We are currently working on this.
We are still performing actions to resolve the stats indexation issue.
We are performing new actions to mitigate the issue. The root cause is partially found.
All stats are now displayed. We are monitoring now.
We are continuing to monitor for any further issues.
The issue is resolved
We are having a production issue right now, the bots are not able to reply to visitors, we are currently investigating the cause
We found the root cause of the issue. Yet, a fix is live. All is working normally. We keep monitoring the production.
This incident has been resolved.
Please know that the video stream conversations between Visitors and Agents are out of order. We are investigating the issue.
The issue has been identified and a fix is being fixed.
This incident has been resolved.
A brief 9-minute incident (from 5p.m to 5:09p.m CET) impacted conversation creation, temporarily preventing visitors from reaching agents. The issue was promptly identified and resolved, and services are now fully operational. We are monitoring the situation to ensure continued stability.
On Thursday, February 13, there were disruptions related to the bots. From 16:54 to 17:38 CET, the chatbots did not receive visitor messages and were unable to respond to conversations. As a result, those conversations were left unanswered and were closed by the auto-closing bot feature.
You may experience some disturbances on conversation routing since 3:39pm CET. We are currently investigating this issue and its impacts. We keep you informed, thanks for your patience and understanding.
A fix has been implemented, and everything is back to normal. You should be able to see notifications on your Website again. We keep monitoring the production. Thank you.
This incident has been resolved since 3:48pm.
It is not possible for visitors to start conversations. This incident is impacting all our services. Our technical team is currently looking into the issue, we will update you as we learn more.
Please note that ongoing conversations are not impacted. Only new conversations can't be created
We found the root cause of the issue. Yet, a fix is live. All is working normally since 2:40pm (CET) We keep monitoring the production.
This incident has been resolved