Kindly outage history

We are currently investigating this issue.

We are investigating an issue where handover requests to Chatwoot live chat are being rejected and closed. End-users may see a message that the handover was cancelled. This affects multiple customers. We recommend adding a temporary notice for end-users informing them about issues with live chat. We will post an update as soon as we have more information.

This incident has been resolved. We applied a fix at 13:39 CEST, and handovers have worked as normal since then. Handover requests to Chatwoot this morning 20.10, may have been closed before an agent could pick them up. You may want to check for affected conversations and follow up with those end-users. If you added a temporary notice about live chat issues, you can now remove it. We are adding monitoring and improving our deployment process to prevent this from happening again. We apologise for the disruption.

We are currently investigating this issue.

We are investigating a potential issue affecting email services from the Kindly platform. We will update you as soon as we have more information.

This issue has been resolved, and email services from the Kindly platform are working as normal.

Due to a domain issue with our "spinnaker script", customers using custom "bubble switch" functions have experienced downtime since Friday 25.09. The issue was fully resolved on September 29 at 13:26 CEST. We apologize for any inconvenience caused. Preventive measures have been put in place to ensure this issue does not occur again.

Salesforce are reporting a service disruption this morning that could affect Salesforce integrations to Kindly. We are monitoring our systems and are seeing an increase errors from our Salesforce integrations. Follow the situation at Salesforce statuspage: https://status.salesforce.com/current/incidents

Salesforce reports restored performance and the integration looks stable.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

Around 13:30 CEST tere was a small bug introduced in a maintenance patch for our Genesys integration, that unfortunately affected all handovers. The bug was quickly solved after discovery around 14:30, and we have introduced regression test to avoid the issue in the future. We apologise for the inconvenience and we will do our best to make sure it doesn't happen again.

Our Voicebot providers are facing performance issues causing certain calls to drop during conversations. We are doing our best to troubleshoot the situation and restore performance. Update: A fix was applied at 14:55, and we are monitoring the situation

Our providers are having performance issues causing degraded bot-performance. We are monitoring the situation and doing our best to restore performance

A fix has been implemented, and we are seeing improved performance. We continue monitoring the situation.

Performance is stable and the incident is resolved.

The issue is identified and we are working on a solution to restore performance.

We are still working on a fix to restore function and working as hard as we can.

Function is restored and we are monitoring the situation.

Performance are restored and stable.

We are working as hard as we can to restore performance

We are still working on restoring optimal performance

We are still experiencing inconsistent performance issues with AI-matching and Bot-outpus. Working as hard as we can to fix

We are still working on the issue causing failed message delivery and error codes in several bots. Coming back with an update as soon as possible

We have implemented a fix and seeing improved performance. We continue monitoring the behavior

This incident has been resolved.

We are experiencing LLM-issues that could affect AI-generated answers and fallback rates

The behaviour seems inconsistent, while we are working on a fix

The behaviour looks more stable, and we are monitoring the situation.

We are continuing to monitor for any further issues.

The behaviour looks more stable, and we are monitoring the behaviour.

This incident has been resolved.

Platform is currently down, we are investigating

We are continuing to investigate this issue.

We are continuing investigating this issue, follow this page for updates

A fix has been implemented and we are monitoring the results

The incident have been resolved. Platform is back up and stable. There will be an internal post-mortem incident report.

The issue has been identified and we are implementing a fix

A fix has been implemented and we are monitoring the results

This incident has been resolved.

On Sunday March 8, some analytics data in Kindly was not updating as expected. This meant dashboards and reporting could show older information than normal during that period. This issue did **not** affect chatbot availability or customer conversations, and no data was lost. Once identified, we restored the sync and updated the delayed analytics data. All systems are now operating normally.

We are currently investigating this issue.

Incident resolved

Because of some reliability changes we are experiencing problems between bubble and server connection, We identified the reason and we are trying to get it out as soon as possible. Due to how browser caching works, it will take some time to get it effective. Thanks for your patience.

A fix has been implemented and we are getting reports of working bots, we are still monitoring

This incident has been resolved.

We are doing a migration on our databases for the Kindly Inbox website. If you are having connection troubles like messages not appearing unless a refresh, we are suggesting logging off and logging in again. If the problems continue please notify us.

This incident has been resolved.

One of our providers responsible for loading our dashboards are having issues atm causing dashboards in your bot not to load. They are aware and working on a fix. No data will be lost. It is only affecting visually loading the data.

Partially solved by the vendor. Several tests show normal behaviour, but it can still occur that the dashboards fail to initialise.

The issue was resolved by the vendor at 21:40 6th of January