Chatbot not working Goodiebox
Timeline · 1 update
- investigating Aug 09, 2026, 02:56 PM UTC
We are currently investigating this issue.
Kindly had 23 outages in the last 2 years totaling 141h 56m of downtime — averaging 0.9 incidents per month.
There were 23 Kindly outages since September 10, 2024 totaling 141h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Our providers are having performance issues cause 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.
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, but there could still be instances of partially degraded performance.
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
Cloudflare has issues, causing part of Kindly among many other services to be down: https://www.cloudflarestatus.com/
We are continuing to work on a fix for this issue.
Bots respond if you managed to load the widget before cloudflare stopped working. From cloudflare: Investigating - Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
All systems seems to be back up, but Claudflare still reports error. Assuming our dependency is solved, while others still waiting. Will monitor going forward.
Down again. Same reason.
Working again. Calling it "partial outage" until Cloudflare is fully up and running.
Update from Cloudflare: We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts.
From Cloudflare: A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.
An employee’s laptop was inadvertently connected directly to their home internet service, bypassing a router/firewall and exposing network ports to the public internet. Automated bots scanning the internet identified an exposed service running inside a Docker container and exploited a vulnerability to deploy a cryptominer within that container. The container held some chatbot configuration files only; it did not contain sensitive or personal data. Our investigation to date shows no evidence of data leakage or any other breach beyond the cryptominer. We are reinforcing endpoint and network configuration requirements to prevent recurrence.
We are currently investigating the issue.
We are continuing to investigate this issue.
Issue seemed to be solved. Currently monitoring and understanding what caused the issue.
This incident has been resolved.
Currently investigating the issue.
No clear reason yet, still investigating
This incident has been resolved.
During a routing maintenance upgrade of the analytics and unexpected event happened that requires us to reboot the database service. While this is ongoing analytics dashboards may be unavailable for some time. During this, all chatbot operations work as normal and all analytics events are recorded in a queue and no data is lost. Only the ability to view the data will be temporarily unavailable.
It has been determined that there is a bug in the analytics database that affects the behavior for how Kindly calculates sessions. We have an open ticket with the database provider where they have acknowledged this bug and are working on a fix, but they don't know how long it will take. In order to restore most of the functionality of the database we have disabled a part of the sessions calculation before resuming normal analytics operations. This will affect stats in dashboards that measure sessions. We will resume ingesting analytics events to still have accurate statistics about messages, fallbacks, labels and all stats that are not derived from sessions. Once a bugfix is available, we plan use the accurate data to recreate the sessions data for the affected period and have accurate sessions statistics, but in the meantime the charts that show sessions may not reflect accurate numbers.
After a normal business day we have looked at the numbers and they seem to be normal. We will continue to monitor the sessions numbers to correct any discrepancies that might have occurred because of the database update issue.
Minor degredation to the analytics pages of Kindly due to partial outage in Kindly's analytics vendor.
While testing out some new features of the analytics systems we accidentally triggered some downtime for the analytics database. Chats are unaffected, and the platform app is working except you can't currently view analytics. APIs for analytics are also temporarily unavailable. No data is lost, all analytical data is being recorded and waiting in a queue to be written to the analytics database once it is online again.
We are continuing to work on a fix for this issue.
The database is now back online and it is possible to make queries again. We will now start writing the queued events to the database.
Database is online, dashboards and APIs function as normal, all queued analytics events have been written to the database.
We experienced degraded performance in our AI services following a faulty deployment, which led to less accurate dialogue matching and AI predictions, such as those from Kindly GPT. We relied on our fallback AI engine system during this period. The issue was identified somewhat late but was resolved shortly after discovery. We will implement measures to detect this kind of degraded performance earlier and reduce its impact.
We are seeing issues where some users experience longer response time from the bot than normal. The issue under investigation. Most users should not be affected.
Still investigating, trying different approaches to find the core issue.
The issue might be related to high traffic, but not clear. Services have been upscaled and we will monitor the changes.
All systems seems stable.
Some users where not able to access the Kindly Platform. Affected users would have experienced the outage for 5 minutes.