Fini AI Outage History
Fini AI is up right nowPingoru has recorded 44 incidents for Fini AI: 8 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 30 of 720 (4%) |
| May 2026 | 1 | 1 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 2 | 0 of 523 (0%) |
Incidents, newest first
Notice October 20, 2026 20 minutes of increased latency or missed replies –
Started Oct 20, 2026, 04:30 PM UTC· resolved Oct 20, 2026, 04:30 PM UTC
- resolved Oct 21, 2026, 08:58 AM UTC
20 minutes of increased latency or missed replies due to server lockup. Fix has been pushed
Major October 14, 2026 Integration and widget processing errors and delays 3m Widget, Chat Integrations with CRMs
Started Oct 14, 2026, 11:29 PM UTC· resolved Oct 14, 2026, 11:32 PM UTC
- investigating Oct 14, 2026, 11:29 PM UTC
We are currently investigating this issue.
- investigating Oct 14, 2026, 11:30 PM UTC
We identified a memory-capacity issue affecting integration processing. Some requests encountered errors or processing delays from 9:10PM UTC - 10:50PM UTC on 14th October, 2026
- identified Oct 14, 2026, 11:30 PM UTC
We identified a memory-capacity issue affecting integration processing. Processing tasks and historical results retained more data than our configured capacity could accommodate.
- monitoring Oct 14, 2026, 11:32 PM UTC
We have increased capacity and confirmed available memory headroom. We are monitoring processing health and reviewing affected requests to determine whether reprocessing is required.
- resolved Oct 14, 2026, 11:32 PM UTC
This incident has been resolved.
- postmortem Oct 14, 2026, 11:46 PM UTC
**Summary** On 14th October, our shared background-processing infrastructure reached its configured memory limit. This caused some requests that depended on background job creation or processing to fail or experience delays. **Customer impact** During the incident, some integration requests could not be successfully queued for processing and returned errors. Background workers also encountered memory-related errors. The full impact window is from 21:10 UTC - 22:50 UTC. **Root cause** Our background-processing system uses Redis to store queued jobs and recent processing history. A concentrated workload generated multiple jobs containing unusually large, repeated copies of conversation history. Completed and failed jobs retained these payloads for diagnostic purposes. At the same time, historical document-processing events were retaining large result payloads separately from their job records. This created substantial baseline memory usage. The combination exhausted Redis’s configured memory limit. Redis then rejected operations that required additional memory, affecting other workloads sharing the instance. Our retention controls limited the **number of jobs and events**, but did not sufficiently constrain their **total memory footprint**. Shared capacity also allowed one workload’s memory consumption to affect others. **Mitigation** The Redis memory limit was increased, and subsequent inspection confirmed available memory headroom. This addressed the immediate capacity constraint. We are separately validating processing recovery and reconciling requests whose queue submission failed or could not be confirmed. **Corrective and preventive actions** The following changes are planned to address the underlying causes: * Reduce queued payloads by storing references instead of repeated conversation histories. * Reduce retained job and event-history data, including large document-processing results. * Introduce stronger workload isolation and per-customer resource controls. * Improve alerts for memory growth, oversized payloads, and queue submission failures. * Reconcile affected requests and reprocess them where appropriate, with duplicate-processing safeguards. Our investigation supports rapid accumulation of oversized retained data as the immediate cause; the source of the repeated workload is fully recovered and functiona
Minor September 29, 2026 Elevated API Errors on Fini Dashboard 44m Dashboard, API, Widget, Chat Integrations with CRMs
Started Sep 29, 2026, 02:16 PM UTC· resolved Sep 29, 2026, 03:01 PM UTC
- investigating Sep 29, 2026, 02:16 PM UTC
We are currently investigating the issue
- resolved Sep 29, 2026, 03:01 PM UTC
This incident has been resolved.
Minor August 18, 2026 Increased latencies in Chat Response Times 32m API, Widget, Chat Integrations with CRMs
Started Aug 18, 2026, 08:04 AM UTC· resolved Aug 18, 2026, 08:37 AM UTC
- investigating Aug 18, 2026, 08:05 AM UTC
We are experiencing spike in chat response times across integrations, widget and API interfaces. We are still working to identify the root cause and will continue to post updates as we learn more and perform mitigation.
- identified Aug 18, 2026, 08:24 AM UTC
We identified the problematic component and have taken corrective actions. There are strong signs of recovery and are working to completely restore the usual latencies. We will post further updates as recovery continues.
- identified Aug 18, 2026, 08:25 AM UTC
We are continuing to work on a fix for this issue.
- resolved Aug 18, 2026, 08:37 AM UTC
The latencies have been normalized after applying mitigations. This incident has been resolved. Thank you for your patience and understanding as we addressed this issue.
Major May 10, 2026 Scheduled maintenance on 10th May, 2026 from 14:30 UTC 49m Dashboard, Widget, Chat Integrations with CRMs
Started May 10, 2026, 03:02 PM UTC· resolved May 10, 2026, 03:52 PM UTC
- investigating May 10, 2026, 03:02 PM UTC
Fini is currently undergoing scheduled maintenance aimed at enhancing system performance and reliability. As part of this maintenance, we are also performing database optimizations to improve query efficiency, stability, and overall response times. During this time, the service may be temporarily unavailable. We apologize for the inconvenience and appreciate your patience and understanding.
- investigating May 10, 2026, 03:21 PM UTC
We are continuing to investigate this issue.
- resolved May 10, 2026, 03:52 PM UTC
The maintenance was completed at 15:40 UTC
Minor April 29, 2026 Slow responses 12h 5m API, Chat Integrations with CRMs
Started Apr 29, 2026, 10:00 PM UTC· resolved Apr 30, 2026, 10:05 AM UTC
- identified Apr 29, 2026, 10:00 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 30, 2026, 10:05 AM UTC
This incident has been resolved.
Minor April 27, 2026 Outage/ no responses from Fini 17h 36m API, Widget, Chat Integrations with CRMs
Started Apr 27, 2026, 09:19 PM UTC· resolved Apr 28, 2026, 02:55 PM UTC
- resolved Apr 27, 2026, 11:27 PM UTC
LLM outage from 27th april 10:30pm UTC to 28th april 00:50am UTC
- postmortem Apr 29, 2026, 12:07 PM UTC
April 27 \(21:19–23:03 UTC\) and April 28 \(13:47–14:55 UTC\), both caused by upstream Azure OpenAI degradation. During those windows Fini didn't reply to a subset of conversations, no incorrect responses were sent, and answer quality was unaffected for threads we did reply to
Critical January 16, 2026 Fini Cloudflare Issue 54m Dashboard, API, Widget, Chat Integrations with CRMs
Started Jan 16, 2026, 09:20 AM UTC· resolved Jan 16, 2026, 10:15 AM UTC
- investigating Jan 16, 2026, 09:20 AM UTC
We are currently seeing an issue in our downstream systems due to an active Cloudflare incident. https://www.cloudflarestatus.com/
- monitoring Jan 16, 2026, 09:59 AM UTC
Seems that the cloudflare issues have been resolved
- resolved Jan 16, 2026, 10:15 AM UTC
This incident has been resolved.
Minor September 22, 2025 Elevated Errors in Gorgias Integration 4h 51m Chat Integrations with CRMs
Started Sep 22, 2025, 06:24 PM UTC· resolved Sep 22, 2025, 11:15 PM UTC
- identified Sep 22, 2025, 06:24 PM UTC
Elevated Errors in Gorgias Integration
- resolved Oct 03, 2025, 11:15 PM UTC
This incident has been resolved.
Major August 21, 2025 Elevated Errors in Intercom Integration 9h 12m Chat Integrations with CRMs
Started Aug 21, 2025, 04:32 AM UTC· resolved Aug 21, 2025, 01:45 PM UTC
- identified Aug 21, 2025, 04:32 AM UTC
Elevated Errors in Intercom Integration
- resolved Oct 03, 2025, 11:16 PM UTC
This incident has been resolved.
Minor July 7, 2025 Elevated Errors in Zendesk Integration 3h 30m Chat Integrations with CRMs
Started Jul 07, 2025, 05:44 PM UTC· resolved Jul 07, 2025, 09:14 PM UTC
- identified Jul 07, 2025, 05:44 PM UTC
Elevated Errors in Zendesk Integration
- resolved Jul 07, 2025, 09:14 PM UTC
This incident has been resolved.
Minor June 12, 2025 Elevated Errors in Hubspot Integration 1h 30m Chat Integrations with CRMs
Started Jun 12, 2025, 08:05 PM UTC· resolved Jun 12, 2025, 09:35 PM UTC
- identified Jun 12, 2025, 08:05 PM UTC
Elevated Errors in Hubspot Integration
- resolved Jun 12, 2025, 09:35 PM UTC
Google cloud had an outage from 6:45am PT 12th June to 2pm PT 12th June which led to Fini not responding to customer chats during this period. This outage has now been resolved
Minor April 15, 2025 Elevated Errors in Livechat Integration 14m Chat Integrations with CRMs
Started Apr 15, 2025, 08:50 AM UTC· resolved Apr 15, 2025, 09:05 AM UTC
- identified Apr 15, 2025, 08:50 AM UTC
Elevated Errors in Livechat Integration
- resolved Apr 15, 2025, 09:05 AM UTC
This incident has been resolved.
Minor January 16, 2025 Critical: Elevated Errors in Zendesk Integration 42m Chat Integrations with CRMs
Started Jan 16, 2025, 07:32 PM UTC· resolved Jan 16, 2025, 08:15 PM UTC
- identified Jan 16, 2025, 07:32 PM UTC
Critical: Elevated Errors in Zendesk Integration
- identified Jan 16, 2025, 07:59 PM UTC
We are seeing rate limiting errors for some specific customers using Zendesk Chat. Not all customers have been affected.
- resolved Jan 16, 2025, 10:45 PM UTC
This incident occured due to Zendesk rate limits for a small set of customers, this has been identified and resolved.
Minor November 12, 2024 Outage in livechat queue –
Started Nov 12, 2024, 02:30 PM UTC· resolved Nov 12, 2024, 02:30 PM UTC
- resolved Nov 14, 2024, 10:27 AM UTC
On 12th Nov 2024, we experienced a temporary 5-minute downtime in our chat queue management service due to scheduled maintenance on our Redis instance by our cloud provider. This led to brief service interruptions in chat-related operations.
- postmortem Nov 14, 2024, 10:27 AM UTC
**Incident Summary** On 12th Nov 2024, we experienced a temporary 5-minute downtime in our chat queue management service due to scheduled maintenance on our Redis instance by our cloud provider. This led to brief service interruptions in chat-related operations. **Impact** During this maintenance window, our chat queues experienced a 5-7 minute delay in processing, resulting in potential delays in customer interactions and response times. We apologize for any inconvenience this may have caused. **Root Cause** The temporary interruption stemmed from our current maintenance configuration with our Redis provider. This configuration includes a brief maintenance window scheduled by the cloud provider approximately every two weeks. **Resolution** To address this, we have scheduled our maintenance window to Sundays at 6 PM Central Time to minimize customer impact during this period. This interim measure will ensure that any potential interruptions occur at a low-traffic time, reducing the likelihood of customer disruption. **Next Steps** We are actively implementing a more robust setup that avoids this scheduled downtime altogether. The upgraded solution will be operational within the next two weeks, ensuring a consistent and uninterrupted chat experience moving forward. **Customer Impact Mitigation** * **Scheduled Maintenance Timing:** Maintenance will occur on Sundays at 6 PM CT to minimize disruption. * **Planned Upgrade:** Implementation of the enhanced setup is already underway, with full deployment expected within two weeks. We appreciate your understanding and patience as we work to enhance our infrastructure to provide you with the best possible service.