Kore.ai Outage History

We are currently experiencing a service disruption affecting the Agent Platform in the US region. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We will continue to provide updates as more information becomes available and progress is made.

Our customers who are all using standalone SearchAI are facing an impact with the Search results across the chats and voice agents. We are actively investigating the issue on our end. Please note that there is no impact on the SearchAI - UXO platform. We will keep you updated once the cause is identified.

Dear USers, We are currently experiencing issues with bot responses across both XO 10 and XO 11UAE instances. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

The investigation is ongoing, and we are working to determine the cause of the issue.

We are currently observing increased latency for multiple services hosted in the Microsoft Azure West US 2 region. This appears to be related to an ongoing Azure platform incident: https://azure.status.microsoft/en-gb/status. Our teams are actively monitoring the situation. At this time, we would like to clarify that there is no service degradation from the Kore application perspective, and the impact is due to external infrastructure factors. We will continue to monitor the situation and keep this page updated.

Dear Users, This is to notify you that the AI4Work product is experiencing intermittent service disruptions currently. We are working on high priority to remediate the issue. We will keep you posted on the resolution.

We are currently investigating the issue.

Dear Users, We are observing that the dashboard and analytics data is not loading for May 18th onwards. The technical team is trying to resolve this on high priority. We will keep you updated. Please note - 1. There is no outage as such. The dashboard and analytics have been observed to be loading data until 17th May 2026. 2. Conversation History API is not impacted. It is pulling the data as expected for 18th and 19th May.

Dear Users, We are experiencing a partial service disruption on SearchAI on US region. XO10 integrations are impacted intermittently. We will keep you updated on the resolution of the incident. We apologize for the inconvenience caused and we appreciate your patience while we work through the resolution.

Hello Users, We are observing degraded performance in the loading of dashboards across XO10 on XO11 in the US region. Please be assured that the experts are looking into it and trying to remediate the issue as soon as possible. We would also like to call out that there is no run-time impact: Bot responses for both digital and IVR type of channels are not impacted. Hence there is no outage as such on the Kore platform.

Update-we are continuing to investigate the issue on high priority. Please be assured that it is a priority for us to remediate the issue.

Our internal monitoring has detected that one of the SBC servers 3.224.189.218 is currently down. We are working with AWS to resolve the issue as soon as possible. The impacted server is in US east 1 region.

We are continuing to investigate the issue with the service provider. More details available at https://health.aws.amazon.com/health/status

Below is the latest update from the Service Provider: We continue to work towards mitigating the increased temperatures to its normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We have weighed away traffic for most services at this time. Customers may experience longer than usual provisioning times. We will provide an update by 7:45 PM PDT, or sooner if we have additional information to share.

We are seeing an outage with our XOCC, where customers are seeing the error "OOM command not allowed when used memory > maxmemory." We will keep you updated as soon as we progress.

We are currently investigating an issue impacting calls on the JP instance. Users may experience failures or delays when attempting to place calls. Our engineering team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.