Kindly Outage History

Kindly is up right now

Kindly had 23 outages in the last 2 years totaling 142h 27m of downtime — averaging 0.9 incidents per month.

There were 23 Kindly outages since June 28, 2024 totaling 142h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kindly.ai

Major May 27, 2026

Performance-issues with AI-matching causing messaging delivery issues and increased fallback rates

Detected by Pingoru
May 27, 2026, 02:32 PM UTC
Resolved
May 27, 2026, 03:51 PM UTC
Duration
1h 18m
Affected: Bot message delivery
Timeline · 4 updates
  1. identified May 27, 2026, 02:32 PM UTC

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

  2. identified May 27, 2026, 02:58 PM UTC

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

  3. monitoring May 27, 2026, 03:00 PM UTC

    Function is restored and we are monitoring the situation.

  4. resolved May 27, 2026, 03:51 PM UTC

    Performance are restored and stable.

Read the full incident report →

Minor May 20, 2026

Performance-issues with AI-matching causing increased fallback rates

Detected by Pingoru
May 20, 2026, 09:30 AM UTC
Resolved
May 20, 2026, 08:47 PM UTC
Duration
11h 16m
Affected: Bot message delivery
Timeline · 6 updates
  1. identified May 20, 2026, 09:30 AM UTC

    We are working as hard as we can to restore performance

  2. identified May 20, 2026, 11:40 AM UTC

    We are still working on restoring optimal performance

  3. identified May 20, 2026, 12:42 PM UTC

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

  4. identified May 20, 2026, 01:08 PM UTC

    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

  5. monitoring May 20, 2026, 01:21 PM UTC

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

  6. resolved May 20, 2026, 08:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026

LLM issues affecting AI-generated answers

Detected by Pingoru
May 19, 2026, 12:18 PM UTC
Resolved
May 19, 2026, 06:39 PM UTC
Duration
6h 21m
Affected: Bot message delivery
Timeline · 6 updates
  1. investigating May 19, 2026, 12:18 PM UTC

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

  2. identified May 19, 2026, 02:13 PM UTC

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

  3. monitoring May 19, 2026, 03:49 PM UTC

    The behaviour looks more stable, but there could still be instances of partially degraded performance.

  4. monitoring May 19, 2026, 04:07 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 19, 2026, 04:07 PM UTC

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

  6. resolved May 19, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 12, 2026

Platform is down

Detected by Pingoru
Mar 12, 2026, 11:09 AM UTC
Resolved
Mar 12, 2026, 12:05 PM UTC
Duration
55m
Affected: Analytics dashboardPlatform app
Timeline · 5 updates
  1. investigating Mar 12, 2026, 11:09 AM UTC

    Platform is currently down, we are investigating

  2. investigating Mar 12, 2026, 11:13 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 12, 2026, 11:35 AM UTC

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

  4. monitoring Mar 12, 2026, 11:43 AM UTC

    A fix has been implemented and we are monitoring the results

  5. resolved Mar 12, 2026, 12:05 PM UTC

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

Read the full incident report →

Minor March 7, 2026

Partial downtime in analytics

Detected by Pingoru
Mar 07, 2026, 09:00 AM UTC
Resolved
Mar 08, 2026, 08:10 PM UTC
Duration
1d 11h
Affected: Analytics dashboard
Timeline · 4 updates
  1. identified Mar 08, 2026, 11:55 AM UTC

    The issue has been identified and we are implementing a fix

  2. monitoring Mar 08, 2026, 12:02 PM UTC

    A fix has been implemented and we are monitoring the results

  3. resolved Mar 08, 2026, 08:10 PM UTC

    This incident has been resolved.

  4. postmortem Mar 09, 2026, 10:59 AM UTC

    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.

Read the full incident report →

Major February 11, 2026

Analytics in Bot Dashboard is down

Detected by Pingoru
Feb 11, 2026, 10:31 AM UTC
Resolved
Feb 11, 2026, 10:33 AM UTC
Duration
2m
Affected: Analytics dashboard
Timeline · 2 updates
  1. investigating Feb 11, 2026, 10:31 AM UTC

    We are currently investigating this issue.

  2. resolved Feb 11, 2026, 10:33 AM UTC

    Incident resolved

Read the full incident report →

Critical January 27, 2026

Communication between chat clients and our servers is overloaded because of a reliability update

Detected by Pingoru
Jan 27, 2026, 11:26 AM UTC
Resolved
Jan 27, 2026, 03:07 PM UTC
Duration
3h 40m
Affected: Bot message delivery
Timeline · 3 updates
  1. identified Jan 27, 2026, 11:26 AM UTC

    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.

  2. monitoring Jan 27, 2026, 11:36 AM UTC

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

  3. resolved Jan 27, 2026, 03:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 26, 2026

Migration on Kindly Inbox Databases

Detected by Pingoru
Jan 26, 2026, 08:31 PM UTC
Resolved
Jan 27, 2026, 11:23 AM UTC
Duration
14h 52m
Affected: Kindly Chat messaging client
Timeline · 2 updates
  1. monitoring Jan 26, 2026, 08:31 PM UTC

    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.

  2. resolved Jan 27, 2026, 11:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 6, 2026

Analytics dashboards fails to load

Detected by Pingoru
Jan 06, 2026, 03:05 PM UTC
Resolved
Jan 07, 2026, 08:37 AM UTC
Duration
17h 32m
Affected: Analytics dashboard
Timeline · 3 updates
  1. identified Jan 06, 2026, 03:05 PM UTC

    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.

  2. monitoring Jan 06, 2026, 05:34 PM UTC

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

  3. resolved Jan 07, 2026, 08:37 AM UTC

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

Read the full incident report →

Critical November 18, 2025

Platform & Chat widget is not accessible

Detected by Pingoru
Nov 18, 2025, 12:01 PM UTC
Resolved
Nov 18, 2025, 03:03 PM UTC
Duration
3h 1m
Affected: Platform appHandover to human chatKindly Chat messaging client
Timeline · 8 updates
  1. identified Nov 18, 2025, 12:01 PM UTC

    Cloudflare has issues, causing part of Kindly among many other services to be down: https://www.cloudflarestatus.com/

  2. identified Nov 18, 2025, 12:01 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Nov 18, 2025, 12:05 PM UTC

    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.

  4. monitoring Nov 18, 2025, 12:12 PM UTC

    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.

  5. identified Nov 18, 2025, 12:27 PM UTC

    Down again. Same reason.

  6. identified Nov 18, 2025, 12:29 PM UTC

    Working again. Calling it "partial outage" until Cloudflare is fully up and running.

  7. identified Nov 18, 2025, 12:36 PM UTC

    Update from Cloudflare: We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts.

  8. resolved Nov 18, 2025, 03:03 PM UTC

    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.

Read the full incident report →

Notice August 27, 2025

Isolated Workstation Configuration Issue

Detected by Pingoru
Aug 27, 2025, 02:47 PM UTC
Resolved
Aug 27, 2025, 02:47 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 27, 2025, 02:47 PM UTC

    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.

Read the full incident report →

Critical April 14, 2025

Handover to human chat are failing

Detected by Pingoru
Apr 14, 2025, 09:29 AM UTC
Resolved
Apr 14, 2025, 10:00 AM UTC
Duration
31m
Affected: Handover to human chat
Timeline · 4 updates
  1. investigating Apr 14, 2025, 09:29 AM UTC

    We are currently investigating the issue.

  2. investigating Apr 14, 2025, 09:32 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 14, 2025, 09:51 AM UTC

    Issue seemed to be solved. Currently monitoring and understanding what caused the issue.

  4. resolved Apr 14, 2025, 12:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2025

Kindly Inbox (Live chat) responds slowly

Detected by Pingoru
Mar 18, 2025, 10:45 AM UTC
Resolved
Mar 18, 2025, 02:02 PM UTC
Duration
3h 16m
Affected: Handover to human chat
Timeline · 3 updates
  1. investigating Mar 18, 2025, 10:45 AM UTC

    Currently investigating the issue.

  2. investigating Mar 18, 2025, 01:43 PM UTC

    No clear reason yet, still investigating

  3. resolved Mar 18, 2025, 05:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 15, 2025

Upgrading analytics database

Detected by Pingoru
Jan 15, 2025, 05:20 PM UTC
Resolved
Jan 16, 2025, 06:47 PM UTC
Duration
1d 1h
Affected: Analytics dashboard
Timeline · 3 updates
  1. identified Jan 15, 2025, 05:20 PM UTC

    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.

  2. monitoring Jan 16, 2025, 12:15 AM UTC

    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.

  3. resolved Jan 16, 2025, 06:47 PM UTC

    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.

Read the full incident report →

Notice January 13, 2025

Minor degredation in analytics pages

Detected by Pingoru
Jan 13, 2025, 10:03 AM UTC
Resolved
Jan 13, 2025, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jan 13, 2025, 10:03 AM UTC

    Minor degredation to the analytics pages of Kindly due to partial outage in Kindly's analytics vendor.

Read the full incident report →

Minor December 11, 2024

Analytics database unplanned maintenance

Detected by Pingoru
Dec 11, 2024, 02:21 PM UTC
Resolved
Dec 11, 2024, 03:10 PM UTC
Duration
48m
Affected: Statistics APIAnalytics dashboard
Timeline · 4 updates
  1. identified Dec 11, 2024, 02:21 PM UTC

    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.

  2. identified Dec 11, 2024, 02:25 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Dec 11, 2024, 02:36 PM UTC

    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.

  4. resolved Dec 11, 2024, 03:10 PM UTC

    Database is online, dashboards and APIs function as normal, all queued analytics events have been written to the database.

Read the full incident report →

Minor November 27, 2024

Degraded performance of AI services

Detected by Pingoru
Nov 27, 2024, 03:18 PM UTC
Resolved
Nov 27, 2024, 01:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 27, 2024, 03:18 PM UTC

    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.

Read the full incident report →

Minor November 14, 2024

Issue with service response times

Detected by Pingoru
Nov 14, 2024, 11:36 AM UTC
Resolved
Nov 14, 2024, 05:46 PM UTC
Duration
6h 9m
Affected: Bot message delivery
Timeline · 4 updates
  1. investigating Nov 14, 2024, 11:36 AM UTC

    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.

  2. investigating Nov 14, 2024, 12:32 PM UTC

    Still investigating, trying different approaches to find the core issue.

  3. monitoring Nov 14, 2024, 02:48 PM UTC

    The issue might be related to high traffic, but not clear. Services have been upscaled and we will monitor the changes.

  4. resolved Nov 14, 2024, 05:46 PM UTC

    All systems seems stable.

Read the full incident report →

Notice September 10, 2024

Issues with access to the Kindly Platform

Detected by Pingoru
Sep 10, 2024, 09:34 AM UTC
Resolved
Sep 10, 2024, 09:34 AM UTC
Duration
Affected: Platform app
Timeline · 1 update
  1. resolved Sep 10, 2024, 09:34 AM UTC

    Some users where not able to access the Kindly Platform. Affected users would have experienced the outage for 5 minutes.

Read the full incident report →

Minor August 6, 2024

Applying changes to dialogues

Detected by Pingoru
Aug 06, 2024, 09:46 AM UTC
Resolved
Aug 06, 2024, 01:54 PM UTC
Duration
4h 7m
Affected: Platform app
Timeline · 3 updates
  1. identified Aug 06, 2024, 09:46 AM UTC

    We experience some issues when applying changes to newly saved dialogues. Your edit will be saved, but it might not have the immediate effect in the bot as you are used to. The queue of applying the changes gets clogged, resulting in some changes taking up the available resources for others (also known as an indexing issue). We are aware of what is wrong and are working on short term and long term fixes to the problem.

  2. identified Aug 06, 2024, 11:27 AM UTC

    We are currently testing a fix in our staging environments.

  3. resolved Aug 06, 2024, 01:54 PM UTC

    The issues is now resolved. All bots using Intents/Kindly Plus should no longer experience any delays. Bots still using samples might experience some delay if lots of changes are applied at the same time.

Read the full incident report →

Minor July 2, 2024

Chat logs not visible

Detected by Pingoru
Jul 02, 2024, 02:05 PM UTC
Resolved
Jul 02, 2024, 03:06 PM UTC
Duration
1h 1m
Affected: Platform app
Timeline · 3 updates
  1. investigating Jul 02, 2024, 02:05 PM UTC

    Users in the platform cannot see history prior to 1st of July. We are working on a solution.

  2. identified Jul 02, 2024, 02:15 PM UTC

    The issue has been identified and a fix is being worked on.

  3. resolved Jul 02, 2024, 03:06 PM UTC

    The issue have been resolved and all chat logs should be visible as normal.

Read the full incident report →