Kore.ai had 71 outages in the last 2 years totaling 33h 19m of downtime — averaging 2.9 incidents per month.
There were 71 Kore.ai outages since July 2, 2025 totaling 33h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
Hi, We are observing a full outage on our XO 11 platform specific to IND Region. Our team is investigating on it. We will keep you the further updates as soon as possible
Hi. The issue was resolved a few minutes ago, and we are currently monitoring the system status.
We identified intermittent issues affecting voice calls on the Kore IVR system via our internal monitoring. The issue impacted a few customer bots operating over the IVR channel. During this period, some users may have experienced sporadic latency and occasional call drops. Incident Timeline: The issue occurred approximately between 11:30 AM and 12:30 PM EST (09:00 PM – 10:00 PM IST). While our experts were investigating, the issue self-resolved. We are sharing this update post-resolution to maintain transparency. Although the incident is resolved, we are actively monitoring the system. Please be assured that we will work internally towards ensuring that this does not happen again. We deeply apologise for any inconvenience that the sporadic issues may have caused.
We have identified an issue with Analytics API's. The issue has been resolved.
We would like to keep our user informed that we are observing a recurrence of service disruptions due to the ongoing outage currently reported by AWS. We are closely monitoring the situation and will provide timely updates on this page as new information becomes available. For more details on the AWS outage, please refer to the official AWS Status Page: https://health.aws.amazon.com/health/status
The Kore services are restored but we are observing some minor latencies and glitches as the AWS continues to restore their services.
We have observed that our Kore Connector service is impacted and our website https://www.kore.ai is down due to the AWS outage. Our SaaS services are functional but the users may face a few temporary glitches or occasional latencies.
Our internal alerts have recovered for Kore connector and the kore.ai website as well. We continue to be on high alert and monitoring the situation over https://health.aws.amazon.com/health/status
As per the latest update from AWS, the mitigation at their end are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. They are applying mitigations to the remaining AZs and are expecting the launch errors and network connectivity issues to subside. Kore internal monitoring alerts are in recovered state but we are continuing to monitor the situation closely over https://health.aws.amazon.com/health/status.
We are receiving positive indicators from AWS that the major impacts in the US-EAST-1 Region are subsiding, especially for services related to new capacity and functions. We are resolving this incident and will continue to closely monitor this stabilization process further over https://health.aws.amazon.com/health/status. Please be assured that we will keep the subscribers informed if we identify any further issue.
Hello Everyone, We are aware of the ongoing outage currently reported by AWS. Our internal teams are actively validating systems to assess any potential impact related to this AWS outage. We are closely monitoring the situation and will provide timely updates on this page as new information becomes available. For more details on the AWS outage, please refer to the official AWS Status Page: https://health.aws.amazon.com/health/status
We have received the following update from AWS: “We continue to observe recovery across most of the affected AWS services. Global services and features that rely on the US-EAST-1 region have also recovered. We are continuing to work toward full resolution and will share further updates as more information becomes available.” Our teams will continue to monitor the situation closely and provide additional updates as necessary.
The AWS team is actively working toward full recovery from EC2 launch errors, which may appear as “Insufficient Capacity” errors. In addition, they are continuing efforts to mitigate increased polling delays affecting AWS Lambda, particularly for Lambda Event Source Mappings with SQS.
AWS is reporting significant progress in resolving the issue that was preventing the launch of new EC2 instances in the US-EAST-1 Region. New instances can now be launched successfully in a number of Availability Zones, and they are actively working to restore the remaining ones. Additionally, the backlog of events for EventBridge and CloudTrail has been cleared, and new events are being delivered normally. We will provide further updates when we receive new information from AWS.
Update - We have not observed any disruptions to our runtime services and our internal monitoring and alerting is also not showing any issues. With this, we are closing this incident. We will continue to monitor the AWS health and status page (https://health.aws.amazon.com/health/status) and will report if we see anything is impacting our services.
This incident has been resolved.
We are observing an intermittent issue with the XO11 SearchAI Dialog GPT. Users are observing an issue with orchestrator. We will keep you posted on the resolution of the issue. We deeply apologize for the inconvenience caused.
This incident has been resolved.
Dear users. We are facing partial service disruption on XO11 currently. We are doing everything we can to remediate the situation. Our sincere apologies for the inconvenience caused.
Please be advised that XO10 remains unaffected.
We are in the process of remediating the situation. We are hopeful that we will be able to remediate the situation shortly. We deeply regret the inconvenience caused.
We are trying our best to expedite remediation. We request your patience while we are doing everything we can to remediate the issue as soon as possible.
We are continuing to work on resolving the issue.
This incident has been resolved.
Hello Users, This is to let you know that we have received a notification from OpenAI that they are facing some service degradation and their APIs are also impacted. The Kore virtual assistants with OpenAI integrations may have an impact. What they have not indicated yet is whether this imapct is global from their end or limited to any geographical location. We are keeping an eye on https://status.openai.com/
We are resolving this incident because as per https://status.openai.com/ the APIs are listed as functional now.
Hello Users, We have been informed that Deepgram is currently experiencing issues with its upstream network provider, impacting multiple US regions. This may cause disruptions to our voice services. Our team is actively monitoring the situation through the Deepgram status page. For real-time updates, Please refer to: https://status.deepgram.com
Current Update from Deepgram: The issue has been mitigated after rerouting traffic to avoid upstream network provider failures.
The issue has been mitigated after rerouting traffic to avoid upstream network provider failures. Networking errors may have occurred intermittently between 12:08 am UTC and 1:51 am UTC.
Only Deepgram SaaS Customers would have been impacted. On-Premise solutions were not impacted. Our team is actively monitoring the situation through the Deepgram status page. For real-time updates, please refer to: https://status.deepgram.com
This incident has been resolved.
We have observed Microsoft TTS errors with some calls when French characters are present in SSML. No issue has been observed for English SSML. Please be assured that we are pursuing a resolution on high priority.
The issue has been resolved. The services have been restored.
The DE region experienced a partial service disruption for around 25 minutes. The situation has been remediated now. During the incident the users may have experienced delayed responses and some chat and calls may have dropped. We apologise for the inconvenience caused.
The DE region experienced a partial service disruption for around 25 minutes. The situation has been remediated now. During the incident the users may have experienced delayed responses and some chat and calls may have dropped. We apologise for the inconvenience caused.
We are currently experiencing an issue impacting incoming calls for customers in Japan using AudioCodes exclusively. Our team is actively investigating the matter and working to restore full service as quickly as possible. No other customers or regions are affected by this disruption. We apologize for any inconvenience and appreciate your patience while we resolve this issue. Please continue to monitor this page for real-time updates.
The services are now back online. Initially, the issue was identified as network-related. We are actively investigating the root cause internally. If any Japan-based customers using AudioCodes are still experiencing problems, please submit a ticket at https://support.kore.ai/.
The services are now back online. Initially, the issue was identified as network-related. We are actively investigating the root cause internally. If any Japan-based customers using AudioCodes are still experiencing problems, please submit a ticket at https://support.kore.ai/.
Dear all, We have identified an issue within the platform (XO-11) affecting the Welcome Voice Test Flow functionality. When initiating a test call, the call is disconnected immediately. Please note, this issue only affects the testing functionality and does not impact end-user interactions or live bot experiences. Our Engineering team is actively working on resolving the issue. We will continue to monitor the situation and provide updates as they become available. Thank you for your understanding.
This incident has been resolved.
We identified an issue with Deepgram TTS following the recent patch release. The issue has since been resolved and functionality has been fully restored.
Dear Users, We have been informed of a global issue currently affecting Microsoft ASR/TTS services. This may impact virtual assistants or solutions on our platform that rely on Microsoft’s ASR/TTS capabilities. Our team is actively working with the relevant stakeholders to resolve this at the earliest. Thank you for your understanding.
This incident has been resolved. We will continue to monitor the situation to ensure stability.
We are currently investigating the issue.
This incident has been resolved.
We are currently investigating this issue.
The investigation is currently ongoing, and we are prioritizing the resolution of this issue as a top priority.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating the issue.
The analysis is ongoing, and we are actively investigating the issue.
The issue has been identified and fix has been implemented
A fix has been implemented. We are monitoring the behaviour.
This incident has been resolved.