Плагины, Webhooks и Handovers терпят неудачу
Pending
- investigating
В настоящее время мы расследуем этот вопрос.
- resolved
Этот инцидент был урегулирован.
Автоматический перевод официального обновления инцидента.
54 Kindly incidents · апрель 2019 г. — official updates, affected components, duration and resolution details.
В настоящее время мы расследуем этот вопрос.
Этот инцидент был урегулирован.
Автоматический перевод официального обновления инцидента.
We are currently investigating this issue.
Около 13:30 CEST tere был небольшим багом, введенным в патч обслуживания для интеграции Genesys, что, к сожалению, повлияло на все передачи. Ошибка была быстро решена после обнаружения около 14:30, и мы ввели регрессионный тест, чтобы избежать проблемы в будущем. Мы приносим извинения за неудобства и сделаем все возможное, чтобы это не повторилось.
Автоматический перевод официального обновления инцидента.
Наши поставщики голосовых ботов сталкиваются с проблемами производительности, из-за которых некоторые звонки падают во время разговоров. Мы делаем все возможное, чтобы устранить ситуацию и восстановить производительность. Обновление: исправление было применено в 14:55, и мы следим за ситуацией
Автоматический перевод официального обновления инцидента.
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
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.
We have identified that when using Telenor as a network provider, our bots will not respond, nor access our platform. We are working on finding out why.
Working on workarounds while getting in contact with Telenor.
Looks to be more companies than Kindly that are affected. Still working on the workaround.
We have confirmed that Telenor is aware of the issue and have internal resources on it. We continue on our workaround in parallel.
Working on the workaround.
Deploying a potential fix and purging the cache.
All systems seems to be back up now. Monitoring to make sure.
All systems stable.
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.
This incident has been resolved. Handover to humans had been failing for 14 minutes.