Kore.ai Outage History

Started Apr 28, 2026, 02:39 PM UTC· resolved Apr 28, 2026, 05:03 PM UTC

1. monitoring Apr 28, 2026, 02:39 PM UTC

   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.

2. monitoring Apr 28, 2026, 03:38 PM UTC

   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.

3. resolved Apr 28, 2026, 05:03 PM UTC

   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.

Read the full incident report →

Started Apr 28, 2026, 05:47 AM UTC· resolved Apr 28, 2026, 07:07 AM UTC

1. investigating Apr 28, 2026, 05:47 AM UTC

   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.

2. monitoring Apr 28, 2026, 05:50 AM UTC

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

3. resolved Apr 28, 2026, 09:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 10:24 PM UTC· resolved Apr 28, 2026, 05:19 AM UTC

1. identified Apr 27, 2026, 10:24 PM UTC

   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.

2. identified Apr 27, 2026, 11:00 PM UTC

   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.

3. monitoring Apr 28, 2026, 03:57 AM UTC

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

4. resolved Apr 28, 2026, 05:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 08:02 PM UTC· resolved Apr 27, 2026, 11:59 PM UTC

1. identified Apr 27, 2026, 08:02 PM UTC

   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.

2. identified Apr 27, 2026, 08:26 PM UTC

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

3. identified Apr 27, 2026, 09:19 PM UTC

   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.

4. identified Apr 27, 2026, 11:01 PM UTC

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

5. resolved Apr 27, 2026, 11:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 24, 2026, 09:40 AM UTC· resolved Apr 24, 2026, 10:36 AM UTC

1. investigating Apr 24, 2026, 09:40 AM UTC

   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.

2. resolved Apr 24, 2026, 10:36 AM UTC

   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

Read the full incident report →

Started Apr 23, 2026, 07:31 PM UTC· resolved Apr 24, 2026, 06:56 AM UTC

1. identified Apr 23, 2026, 07:31 PM UTC

   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.

2. resolved Apr 24, 2026, 06:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 08:09 AM UTC· resolved Apr 22, 2026, 08:19 AM UTC

1. identified Apr 22, 2026, 08:09 AM UTC

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

2. resolved Apr 22, 2026, 08:19 AM UTC

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

Read the full incident report →

Started Apr 13, 2026, 05:18 PM UTC· resolved Apr 13, 2026, 05:18 PM UTC

1. monitoring Apr 13, 2026, 05:18 PM UTC

   Hello Users, This is to keep you informed that an issue with DataTables connectivity from the bot or app was identified after the release XO Platform Release (10.24.1/11.23.1). This may have impacted some apps or bots that have used the data tables in their main workflows. Please note - The data table public API was not impacted. In the US region, the changes have been rolled back already and the issue is not observed any further.

2. resolved Apr 13, 2026, 05:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 03:42 PM UTC· resolved Apr 07, 2026, 03:42 PM UTC

1. resolved Apr 07, 2026, 03:42 PM UTC

   Dear Users, We observed degraded performance on the XO 11 platform in the DE instance between 08:35 PM IST and 08:45 PM IST. The issue has been identified and resolved. We sincerely apologize for any inconvenience caused. Our team will continue to closely monitor the system to ensure continued stability.

Read the full incident report →

Started Apr 07, 2026, 01:48 PM UTC· resolved Apr 07, 2026, 01:48 PM UTC

1. resolved Apr 07, 2026, 01:48 PM UTC

   Dear Users, We observed intermittent issues on the XO 11 platform in the India instance between 06:40 PM IST and 07:05 PM IST. There was no impact to runtime services for customers in the India Production environment. However, the search functionality within the “Interactions” tab was intermittently affected during this time. The issue has been identified and resolved. We sincerely apologize for any inconvenience caused. Our team will continue to closely monitor the system to ensure stability.

Read the full incident report →

Started Apr 06, 2026, 02:21 AM UTC· resolved Apr 06, 2026, 06:59 AM UTC

1. investigating Apr 06, 2026, 02:21 AM UTC

   We are currently experiencing a partial disruption affecting UXO/XO11 SmartAssist IVR calls in the JP region. Our team is actively investigating the issue and working towards a resolution at the earliest. We sincerely apologize for the inconvenience caused and appreciate your patience. Further updates will be shared as they become available.

2. investigating Apr 06, 2026, 02:43 AM UTC

   We would like to inform you that an outage has been reported impacting UXO/XO11 in the JP region. Our team is actively investigating the issue and working to restore services at the earliest. We sincerely apologize for the inconvenience caused and appreciate your patience. Further updates will be shared as they become available.

3. investigating Apr 06, 2026, 03:44 AM UTC

   We are continuing to investigate this issue.

4. monitoring Apr 06, 2026, 03:50 AM UTC

   The XO11 platform in the JP region now appears to be stable. However, customers using the Agentic Platform may continue to experience issues. Our team is actively investigating and working to address the remaining impact, while we continue to closely monitor the status of the XO11 platform. We appreciate your patience and will share further updates as more information becomes available

5. monitoring Apr 06, 2026, 06:47 AM UTC

   We are continuing to monitor the system’s stability and validations are currently in progress.

6. resolved Apr 06, 2026, 06:59 AM UTC

   This incident has been resolved. We will continue to monitor the system’s stability.

Read the full incident report →

Started Apr 02, 2026, 06:05 AM UTC· resolved Apr 02, 2026, 06:05 AM UTC

1. resolved Apr 02, 2026, 06:05 AM UTC

   Dear Users, We would like to inform you about a recently reported supply chain security incident involving the Axios npm package. As per available information, Axios versions 1.14.1 and 0.30.4 were briefly published around March 30–31, 2026. These versions did not follow the standard release process (no corresponding GitHub release artifacts) and were subsequently removed from npm. It has been reported that these versions introduced a dependency on a potentially malicious package. Kore has completed validation across our systems and can confirm that none of our applications use the affected Axios versions (1.14.1 or 0.30.4). There is no impact to our products or services from this incident. We will continue to monitor the situation and take appropriate actions if needed. Thank you for your continued trust and support.

Read the full incident report →

Started Mar 30, 2026, 04:00 PM UTC· resolved Mar 30, 2026, 06:36 PM UTC

1. investigating Mar 30, 2026, 04:57 PM UTC

   Users may experience intermittent response delays and performance latency at this time. Our teams are actively working on mitigation efforts to restore services to normal operation. During this period, Agent AI services including Sentiment Analysis, Agent Coaching, and Quality Management may operate with limited functionality, and some features may be temporarily unavailable. We truly appreciate your patience and understanding as we work to fully restore services. Please be assured that our teams are prioritizing this and are working diligently to resolve the issue as quickly as possible. We will continue to keep you informed with regular updates on the progress.

2. investigating Mar 30, 2026, 05:00 PM UTC

   We are continuing to actively investigate this issue. We sincerely appreciate your patience and understanding as we work towards fully restoring services. Please be assured that our teams are treating this with the highest priority and are making every effort to resolve it as quickly as possible.

3. investigating Mar 30, 2026, 05:29 PM UTC

   Our teams are continuing to thoroughly investigate the issue. We greatly appreciate your patience and understanding during this time. Please rest assured that this is being treated with the highest priority, and every effort is being made to restore services as quickly as possible.

4. investigating Mar 30, 2026, 05:46 PM UTC

   On the US SaaS instance, partial service disruptions are currently being observed across both XO10 and XO11, with differing symptoms in each. For XO10, customers using Agent Desktop and AgentAI may experience impact, particularly with agent assignment, routing, and agent coaching functionalities. For XO11, certain Agent AI services including Sentiment Analysis, Agent Coaching, and Quality Management may operate with limited functionality, and some features could be temporarily unavailable. Based on our current assessment, customers not using the above-mentioned functionalities or components should not be impacted. We appreciate your patience and will continue to keep you updated as we make progress.

5. monitoring Mar 30, 2026, 06:26 PM UTC

   The issue has been resolved. We will continue to closely monitor system performance to ensure stability.

6. resolved Mar 30, 2026, 06:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 28, 2026, 11:00 PM UTC· resolved Mar 28, 2026, 11:00 PM UTC

1. resolved Mar 28, 2026, 11:28 PM UTC

   Dear Users, We would like to inform you that a service disruption was experienced on the US instance, which lasted approximately 20 minutes. Corrective measures have now been implemented. The system is currently under monitoring to ensure stability.

Read the full incident report →

Started Mar 24, 2026, 07:36 PM UTC· resolved Mar 24, 2026, 07:59 PM UTC

1. monitoring Mar 24, 2026, 07:36 PM UTC

   Dear Users, Several users have reported that Kore bots were not responding on MS Teams between 12:00 pm EST and 3:30 pm EST today (24 March 2026). Now the bots seem to be responding. However, there may still be sporadic incidents for bots not responding on the MS Teams channel. This is to clarify and confirm that the issue is not from Kore's end. We have observed errors on MS Teams channel across all our bots across regions. We have also been monitoring MS Teams status but we have not received any outage notification from Microsoft as well. We apologize for any inconvenience caused due to this incident. We are continuously monitoring the bot responses on MS Teams and we will keep you posted.

2. resolved Mar 24, 2026, 07:59 PM UTC

   After 3:38 PM EST we have not observed any errors on our logs. This incident stands resolved. We will continue to monitor the logs and update the status page if we see any further issues.

Read the full incident report →

Started Mar 13, 2026, 12:30 PM UTC· resolved Mar 13, 2026, 12:30 PM UTC

1. resolved Mar 13, 2026, 01:54 PM UTC

   Hello Users, We would like to inform you that some users may have experienced intermittent issues while accessing Dashboards/Analytics, including occasional difficulty viewing dashboards. Our team promptly investigated the matter, and we are happy to share that the issue has now been identified and resolved. Services should be functioning normally at this time. We sincerely apologize for any inconvenience this may have caused and truly appreciate your patience and understanding while we worked to address the issue. If you continue to experience any problems or have further questions, please feel free to reach out to the support team, and we will be glad to assist you. Thank you for your continued support.

Read the full incident report →

Started Mar 04, 2026, 04:15 AM UTC· resolved Mar 04, 2026, 06:09 AM UTC

1. investigating Mar 04, 2026, 04:15 AM UTC

   Our IND region UXO is down since a few minutes. We are currently investigating the issue on our end. We will keep you updated the progress in the next 15 minutes.

2. identified Mar 04, 2026, 04:41 AM UTC

   The issue has been identified and our team is actively working on fixing it. We will keep you updated as soon as we progress.

3. monitoring Mar 04, 2026, 05:04 AM UTC

   The issue has been fixed on our end, and we are monitoring the progress.

4. resolved Mar 04, 2026, 06:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 08:01 AM UTC· resolved Mar 25, 2026, 02:06 AM UTC

1. investigating Mar 02, 2026, 08:01 AM UTC

   Dear Valued Users, We would like to inform you that due to an ongoing service disruption with our service provider, some users may be experiencing partial outages across the UAE region. Our provider has advised that a localized power issue has now impacted an additional Availability Zone within the ME-CENTRAL-1 Region (mec1-az3). As a precautionary measure, we had previously redirected traffic to the other available zones within the UAE region. However, the provider has recently confirmed that two out of the three zones are currently affected. At this time, our traffic has been routed to the remaining operational zone, which is running with limited availability. Please be assured that the service provider is actively working to restore full functionality. Our team is closely coordinating with them and continuously monitoring the situation to minimize the impact wherever possible. During this period, some users may continue to experience intermittent or partial disruptions until full service restoration is achieved. We sincerely apologize for any inconvenience this may cause and truly appreciate your patience and understanding. We will keep you informed with further updates as they become available.

2. investigating Mar 02, 2026, 08:51 AM UTC

   We are experiencing full outage and we are continuing to investigate the issue with the service provider. Below is the latest update from the AWS Status Page: https://health.aws.amazon.com/health/status We will provide further updates as soon as progress is made.

3. investigating Mar 02, 2026, 11:09 AM UTC

   We are actively working with the service provider to achieve full service recovery and will share further updates as progress is made. AWS Status Page: https://health.aws.amazon.com/health/status

4. investigating Mar 09, 2026, 07:27 AM UTC

   Dear Valued Customers, We would like to inform you that we are currently experiencing a service disruption affecting part of our infrastructure hosted in the AWS Middle East region. At the moment, this issue appears to be related to an outage impacting two out of the three Availability Zones within the ME Central region. As a result, some customers hosted in this region may experience temporary service unavailability. We completely understand how important service availability is for your day-to-day operations, and we sincerely regret any inconvenience this situation may be causing. At this time, AWS has not yet provided a confirmed estimated time for full recovery. However, please be assured that our engineering and operations teams are actively working to minimize the impact. We are closely monitoring the situation, coordinating directly with AWS support teams, and exploring all possible options to restore services as quickly and safely as possible. Current Impact: Customers hosted in the AWS Middle East region may experience service degradation or temporary unavailability. Services hosted in other regions remain unaffected and continue to operate normally. Actions We Are Taking: Continuously monitoring the infrastructure and maintaining close communication with AWS for the latest updates. Actively evaluating and implementing mitigation strategies to restore services. Working on shifting affected workloads where possible to reduce the impact on customers. We truly appreciate your patience and understanding while this situation is being resolved. Our team is fully engaged and committed to restoring normal operations as quickly as possible. We will continue to share updates as more information becomes available. Thank you for your continued support and cooperation.

5. resolved Mar 25, 2026, 02:06 AM UTC

   Dear Valued Customers, The earlier service disruption affecting part of our infrastructure in the AWS Middle East region has now been fully resolved. All impacted services have been successfully restored, and the platform is operating normally. Our teams have verified system stability and will continue to monitor closely to ensure consistent performance. Our Customer Success Team will proactively reach out to affected customers to provide guidance and support as needed. We sincerely apologize for any inconvenience caused and truly appreciate your patience and understanding throughout this incident. If you continue to experience any issues, please reach out to our support team. Thank you for your continued support.

Read the full incident report →

Started Mar 01, 2026, 01:44 PM UTC· resolved Mar 01, 2026, 04:37 PM UTC

1. investigating Mar 01, 2026, 01:44 PM UTC

   We are currently experiencing performance degradation on our UAE instance due to a disruption from our service provider. Our team is actively working with the provider to resolve the issue as quickly as possible. We will share further updates as soon as more information becomes available. Thank you for your patience.

2. monitoring Mar 01, 2026, 03:04 PM UTC

   At this time, we have validated our bots and are not observing any latency. The service provider has reported a localized power issue affecting one Availability Zone (mec1-az2) in the ME-CENTRAL-1 region, causing temporary connectivity issues and elevated error rates for certain resources. Other Availability Zones remain unaffected, and traffic has been shifted where possible. Restoration efforts are ongoing, with recovery expected to take several hours. We will continue to closely monitor the situation and provide further updates as needed. Service Provider Status Page: https://health.aws.amazon.com/health/status

3. resolved Mar 01, 2026, 04:37 PM UTC

   The service provider has confirmed that restoration efforts are currently in progress and are expected to take several hours. Although there is no impact on end users at Kore, we have proactively redirected traffic to a different region to prevent any unforeseen discrepancies. Kore Team will continue to monitor the situation closely in coordination with the service provider. This incident thread will now be closed. Should any additional issues arise in the meantime, a new incident will be opened and communicated promptly.

Read the full incident report →

Started Feb 10, 2026, 06:33 AM UTC· resolved Feb 10, 2026, 07:03 AM UTC

1. investigating Feb 10, 2026, 06:33 AM UTC

   We are currently investigating intermittent login issues impacting users attempting to access the Agent Platform on the DE instance. Users are experiencing login failures. The team is actively analysing application logs, service health, and infrastructure components to identify the underlying cause and restore stable access at the earliest. Further updates will be shared as the investigation progresses.

2. resolved Feb 10, 2026, 07:03 AM UTC

   The issue has been resolved. We will continue to monitor the behaviour.

Read the full incident report →

Started Jan 12, 2026, 07:43 AM UTC· resolved Jan 12, 2026, 08:05 AM UTC

1. investigating Jan 12, 2026, 07:43 AM UTC

   We are currently experiencing an issue affecting agent login on the Agent Platform in the DE region. Our teams are actively investigating and working to resolve the issue. The next update will be shared within the next 15 to 30 minutes.

2. resolved Jan 12, 2026, 08:05 AM UTC

   The issue has been fixed on our end, and we are monitoring its progress.

Read the full incident report →

Started Jan 06, 2026, 12:15 PM UTC· resolved Jan 06, 2026, 12:15 PM UTC

1. resolved Jan 06, 2026, 02:44 PM UTC

   This is to notify the users that we observed an "intermittent" issue with the agent platform SSO login that lasted for about 60 minutes starting (05:45 PM IST; 07:15 AM JAN/06/2026 EST). We deeply regret the inconvenience caused. Please be assured that this has been resolved around 06:45 PM IST, promptly after it was reported, and we do not see any possibility of recurrence. Please also note that the issue was only with SSO login and this did not impact any runtime functionality.

Read the full incident report →

Started Jan 05, 2026, 05:15 PM UTC· resolved Jan 05, 2026, 06:03 PM UTC

1. investigating Jan 05, 2026, 05:27 PM UTC

   We are currently experiencing issues on XO Platform, XOCC, Agent Platform for the US Region. Our team is actively working on resolving the issue. We apologize for any inconvenience and will post another update as soon as we learn more. Please check our status page for the most up-to-date information: [https://status.kore.com]

2. investigating Jan 05, 2026, 05:37 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 05, 2026, 05:38 PM UTC

   We are continuing to investigate this issue.

4. investigating Jan 05, 2026, 05:49 PM UTC

   The issues affecting the Agent Platform have been resolved. The teams are actively working on addressing the issues observed with the XO and XOCC platforms.

5. investigating Jan 05, 2026, 06:14 PM UTC

   All platforms are now up and running. We are currently observing some latency, and our teams are actively working on priority to address the performance degradation. Thank you for your patience and continued understanding.

6. monitoring Jan 05, 2026, 06:35 PM UTC

   All reported issues have been resolved, and we will continue to closely monitor the situation to ensure stability.

7. resolved Jan 05, 2026, 07:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 02, 2026, 06:00 PM UTC· resolved Jan 02, 2026, 06:00 PM UTC

1. resolved Jan 02, 2026, 06:14 PM UTC

   Dear Users, We experienced a service disruption impacting the Semantic Search functionality due to a partial outage at our service provider, Pinecone. The issue was promptly identified and has now been fully resolved by the provider. You can find the incident details at the link below: https://status.pinecone.io/incidents/rsjfq0mjpln5 We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding.

Read the full incident report →

Started Jan 02, 2026, 05:43 AM UTC· resolved Jan 02, 2026, 08:26 AM UTC

1. investigating Jan 02, 2026, 05:43 AM UTC

   We are currently experiencing a design-time issue affecting the Agent Platform. Our engineering team is actively investigating and working to resolve the issue. Please note that there is no end-user impact. We will share updates as progress is made. We apologize for any inconvenience and appreciate your patience.

2. monitoring Jan 02, 2026, 06:20 AM UTC

   We have identified and fixed the design-time issue affecting the Agent Platform. We are monitoring it closely.

3. resolved Jan 02, 2026, 08:26 AM UTC

   As this has already been fixed, we are closing this incident.

Read the full incident report →