Is Fini AI down?

20 minutes of increased latency or missed replies due to server lockup. Fix has been pushed

We are currently investigating this issue.

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

We identified a memory-capacity issue affecting integration processing. Processing tasks and historical results retained more data than our configured capacity could accommodate.

We have increased capacity and confirmed available memory headroom. We are monitoring processing health and reviewing affected requests to determine whether reprocessing is required.

This incident has been resolved.

**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

We are currently investigating the issue

This incident has been resolved.

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.

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.

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

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.