Kindly Outage History

Kindly is up right now

Kindly had 12 outages in the last 2 years totaling 98h 31m of downtime — averaging 0.5 incidents per month.

There were 12 Kindly outages since August 27, 2025 totaling 98h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kindly.ai

Minor June 11, 2026

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

Detected by Pingoru
Jun 11, 2026, 03:25 PM UTC
Resolved
Jun 11, 2026, 06:01 PM UTC
Duration
2h 35m
Affected: Bot message delivery
Timeline · 3 updates
  1. identified Jun 11, 2026, 03:25 PM UTC

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

  2. monitoring Jun 11, 2026, 03:45 PM UTC

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

  3. resolved Jun 11, 2026, 06:01 PM UTC

    Performance is stable and the incident is resolved.

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 →