Kore.ai Status

Resolved: This incident has been resolved.

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

Identified: Apologies that it is taking more time than anticipated. We are continuing to investigate. Thank you for your patience while we work on remediating the issue.

Identified: We are continuing to investigate on high priority. We will keep you updated on the resolution of the issue.

Identified: Dear Users, We would like to inform that we are observing intermittent issues while loading few of our our analytics/dashboards. There is no impact observed for the end users of the bot. So the bot availability or run-time should not be a concern. We are investigating the matter on high priority and will keep you posted on the resolution of the issue.

Resolved: This incident has been resolved.

Identified: Update - We continue to work with AWS to remediate the issue.

Revised impact assessment:

1. The dashboards and analytics will load but any transaction data on of after 9:40 am EST 28 Apr 2026 will not be reported on the dashboard until this issue is resolved.
2. Ability to export dashboard data may be impacted.
3. Custom dashboards may also be impacted.

Identified: Dear Users, In our US region, we are observing a sync failure with our data-lake that caters to dashboards and analytics. We are engaged with AWS to understand the root cause and remediate as soon as possible. Impact: The dashboards and analytics will load but any transaction data on of after 9:40 am EST 28 Apr 2026 will not be reported on the dashboard until this issue is resolved.

Resolved: This incident has been resolved.

Monitoring: The issue has been identified and mitigated. We will continue to monitor the system to ensure stability.

Investigating: 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.

Resolved: Inbound and outbound traffic are currently stable from our end. While the issue has been resolved, we'll continue to monitor the situation to ensure stability

Investigating: 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.

Resolved: This incident has been resolved.

Monitoring: We identified the issue and a solution has been implemented. Currently, we are monitoring the situation

Investigating: 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.

Resolved: The issue has been fixed, and we are currently monitoring the progress.

Identified: Our SearchAI services were impacted and experiencing intermittent disruptions specific to the Knowledge Chunk retrievals. We identified the issue and working on fixing it

Resolved: This incident has been resolved.

Identified: An issue with Microsoft ASR confidence scores in the East region has been reported by multiple customers using our BankAI solution over IVR.

This has been identified as an issue from Microsoft’s end. During our working session, the Microsoft support team acknowledged the problem and is actively working on a fix, although it has not yet been reflected on their status page.

For BankAI customers, as an interim mitigation, we have i implemented workaround by handling the minimum confidence score.

Other Kore customers using Microsoft ASR in the US East region and relying on confidence scores may also experience similar issues. A possible workaround can be to reduce the minimum confidence score threshold (e.g., set it to 0.01) to allow calls to proceed and minimize impact.

Resolved: This incident has been resolved.

Monitoring: Based on our monitoring, we don't see any further failures on our end.

Identified: Update - we continue to observe intermittent failures while calling Azure OpenAI APIs. We are monitoring and will inform as soon as we observe stability of the Azure OpenAI APIs.

Identified: Dear Users,

This is to keep you updated that we have a lot of reports coming in for Azure OpenAI failures. We would like to inform the users that the issue is not from Kore’s end.

Azure OpenAI has not declared any outage at their end yet but we have confirmed that the APIs when called from tools like postman are erroring out.

We would like to additionally call out that this incident is different from the dashboard or analytics issue we are mitigating on another incident thread.

Resolved: Update - The error rates have significantly improved as per our internal monitoring. Except for 1-2 LLM errors every 5 minutes, we do not see much Platform wide issue for Azure LLM failures. Hence we are closing this incident. We will continue to monitor the system for further errors and we will keep our users updated in case we see any recurrence pattern.

Monitoring: Dear users, We are observing a reduction in the frequency of errors but we still see LLM errors via our internal monitoring. Please be assured that we are keeping a watch on this and we will continue to keep you posted.

Monitoring: Dear users,

We have incoming reports from several customers and developers that Microsoft Azure APIs are not working.

Microsoft did not put out any status update. But through publicly available information, it is evident that there are issues being observed currently.

After yesterday, apparently there is a recurrence. We are monitoring at our end every hour, and we will keep you updated on our observations.

Please note that although our bots may be impacted if Microsoft Azure services are being consumed, this issue is not from our end.

Resolved: Update - The error rates have significantly improved as per our internal monitoring. Except for 1-2 LLM errors every 5 minutes, we do not see much Platform wide issue for Azure LLM failures. Hence we are closing this incident. We will continue to monitor the system for further errors and we will keep our users updated in case we see any recurrence pattern.

Monitoring: Dear users, We are observing a reduction in the frequency of errors but we still see LLM errors via our internal monitoring. Please be assured that we are keeping a watch on this and we will continue to keep you posted.

Monitoring: Dear users,

We have incoming reports from several customers and developers that Microsoft Azure APIs are not working.

Microsoft did not put out any status update. But through publicly available information, it is evident that there are issues being observed currently.

After yesterday, apparently there is a recurrence. We are monitoring at our end every hour, and we will keep you updated on our observations.

Please note that although our bots may be impacted if Microsoft Azure services are being consumed, this issue is not from our end.

Resolved: This incident has been resolved.

Monitoring: Based on our monitoring, we don't see any further failures on our end.

Identified: Update - we continue to observe intermittent failures while calling Azure OpenAI APIs. We are monitoring and will inform as soon as we observe stability of the Azure OpenAI APIs.

Identified: Dear Users,

This is to keep you updated that we have a lot of reports coming in for Azure OpenAI failures. We would like to inform the users that the issue is not from Kore’s end.

Azure OpenAI has not declared any outage at their end yet but we have confirmed that the APIs when called from tools like postman are erroring out.

We would like to additionally call out that this incident is different from the dashboard or analytics issue we are mitigating on another incident thread.