Kore.ai Outage History

Kore.ai is up right now

Kore.ai had 72 outages in the last 2 years totaling 91h 12m of downtime — averaging 3 incidents per month.

There were 72 Kore.ai outages since July 27, 2025 totaling 91h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kore.com

Minor July 1, 2026

UAE Region - Intermittent response drops were obeserved for some time.

Detected by Pingoru
Jul 01, 2026, 07:35 PM UTC
Resolved
Jul 02, 2026, 04:14 AM UTC
Duration
8h 38m
Timeline · 1 update
  1. resolved Jul 01, 2026, 07:35 PM UTC

    This is to notify the users of the UAE region that their apps or bots may have faced intermittent issues like sporadic response failures or call drops in the UAE region. Incident lasted for approximately 28 minutes between Wed Jul 1, 2026 2:44 PM EST to Wed, Jul 1, 2026 3:12 PM EST. This incident was internally identified by our proactive monitoring. Note - There is no outage right now and the alert has recovered. We are continuing to monitor the environment. We sincerely apologize for any inconvenience caused and thank you for your continued trust in us.

Read the full incident report →

Major July 1, 2026

Kore Japan Region - Kore Voice gateway service is experiencing a partial service disruption

Detected by Pingoru
Jul 01, 2026, 08:16 AM UTC
Resolved
Jul 02, 2026, 11:26 AM UTC
Duration
1d 3h
Affected: Kore IVR
Timeline · 3 updates
  1. investigating Jul 01, 2026, 08:16 AM UTC

    **Kore Japan Region:** We are again experiencing a recurring partial disruption affecting both inbound and outbound calling through the Kore Voice Gateway service. We understand the impact this may have on your operations and sincerely apologize for the inconvenience. Our engineering and operations teams are actively investigating the issue, working to identify the underlying cause, and implementing remediation measures to restore full service as quickly as possible. We will continue to provide timely updates as more information becomes available and appreciate your patience and understanding.

  2. monitoring Jul 01, 2026, 10:14 AM UTC

    Kore Japan Region: Mitigation measures have been implemented for the issue affecting inbound and outbound voice calling services, and operations are currently stable. Our teams remain actively engaged and are closely monitoring the environment to validate the effectiveness of the fix and ensure ongoing service reliability. We appreciate your continued patience and will provide further updates if necessary.

  3. resolved Jul 02, 2026, 11:26 AM UTC

    The issue impacting inbound and outbound calling services through the Kore Voice Gateway in the Japan region has been resolved. No further issues have been observed by our monitoring systems or reported by customers during the extended monitoring period. We appreciate your patience, cooperation, and understanding throughout this incident.

Read the full incident report →

Minor July 1, 2026

Intermittent Issues Affecting App/Bot Training on JP Search Instance

Detected by Pingoru
Jul 01, 2026, 06:32 AM UTC
Resolved
Jul 01, 2026, 09:27 AM UTC
Duration
2h 54m
Affected: Search Service
Timeline · 4 updates
  1. investigating Jul 01, 2026, 06:17 AM UTC

    We are currently observing intermittent issues affecting the App/Bot Training on the JP Search instance. Our engineering team is actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

  2. monitoring Jul 01, 2026, 06:32 AM UTC

    The App/Bot Training issue has been resolved, and the affected functionality has been restored. Our teams will continue to closely monitor the system to ensure stability and verify that the issue does not recur.

  3. monitoring Jul 01, 2026, 06:32 AM UTC

    We are continuing to monitor the system to ensure stability

  4. resolved Jul 01, 2026, 09:27 AM UTC

    This incident has been resolved at 11:45 AM IST.

Read the full incident report →

Major July 1, 2026

Intermittent Issues Affecting Analytics on IND Instance

Detected by Pingoru
Jul 01, 2026, 05:50 AM UTC
Resolved
Jul 01, 2026, 08:23 AM UTC
Duration
2h 32m
Affected: Analytics
Timeline · 3 updates
  1. investigating Jul 01, 2026, 05:50 AM UTC

    We are currently observing intermittent issues affecting the Analytics section on the IND instance. Our teams are actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible. Please note that there is no impact on platform runtime. We will continue to provide updates as more information becomes available.

  2. monitoring Jul 01, 2026, 07:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 01, 2026, 08:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026

US Central Region - Call recording availability is impacted

Detected by Pingoru
Jun 30, 2026, 05:17 PM UTC
Resolved
Jun 30, 2026, 05:40 PM UTC
Duration
23m
Affected: Kore IVR
Timeline · 4 updates
  1. investigating Jun 30, 2026, 05:17 PM UTC

    Dear Users, We want to let you know that the bot developers and admins are currently facing issues in accessing the call recording in the XOCC dashboard in the US Central region. We are addressing this issue as soon as possible. We will keep you posted. Please note that there is no impact on service availability in general and runtime is not impacted.

  2. monitoring Jun 30, 2026, 05:21 PM UTC

    We identified the issue and fixed it. Currently, we are monitoring the progress

  3. monitoring Jun 30, 2026, 05:28 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 30, 2026, 05:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2026

US Region (Standalone SearchAI) - Brief intermittent service disruptions observed on Standalone SearchAI apps

Detected by Pingoru
Jun 25, 2026, 09:28 PM UTC
Resolved
Jun 25, 2026, 09:15 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 25, 2026, 09:28 PM UTC

    This is to keep our users updated that we observed a brief partial service disruption on Standalone SearchAI on our US region between Thu, Jun 25, 2026 4:52:09 PM EST and Thu, Jun 25, 2026 5:00:26 PM EST. Some search integration calls may have failed during this time. We sincerely apologize for the inconvenience caused due to this brief partial service disruption

Read the full incident report →

Major June 12, 2026

US Region - AI for Process (AI4P) service disruption

Detected by Pingoru
Jun 12, 2026, 09:23 PM UTC
Resolved
Jun 11, 2026, 08:40 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 12, 2026, 09:23 PM UTC

    We would like to report an incident that we observed with AI for Process product on 11 June between 4:40 AM IST and 1:49 PM IST. The automation executions were impacted. On successful resolution of the incident, the automations resumed. We deeply apologize for the inconvenience caused by this incident to our AI4P users and customers. We are doing everything we can to avoid any recurrence of such incidents.

Read the full incident report →

Critical June 11, 2026

Experiencing Outage with Kore.ai Agent Platform On US Region

Detected by Pingoru
Jun 11, 2026, 12:26 AM UTC
Resolved
Jun 11, 2026, 01:02 AM UTC
Duration
36m
Affected: Agentic AppToolModel StudioPrompt StudioEvaluationStudioAdminDatasetSearch AI
Timeline · 2 updates
  1. investigating Jun 11, 2026, 12:26 AM UTC

    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.

  2. resolved Jun 11, 2026, 01:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 5, 2026

Kore.ai is Investigating on the Issue with Standalone SearchAI Causing No Search Results Across Chat and Voice Agents with US Region

Detected by Pingoru
Jun 05, 2026, 05:38 PM UTC
Resolved
Jun 05, 2026, 07:07 PM UTC
Duration
1h 28m
Affected: Search Service
Timeline · 4 updates
  1. investigating Jun 05, 2026, 05:38 PM UTC

    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.

  2. identified Jun 05, 2026, 06:34 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 05, 2026, 06:48 PM UTC

    We are monitoring the results.

  4. resolved Jun 05, 2026, 07:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 4, 2026

Investigating issues with XO 10 Platform on the UAE Instance.

Detected by Pingoru
Jun 04, 2026, 01:30 AM UTC
Resolved
Jun 04, 2026, 02:07 AM UTC
Duration
37m
Affected: Bot UptimeBot Builder
Timeline · 4 updates
  1. investigating Jun 04, 2026, 01:30 AM UTC

    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.

  2. investigating Jun 04, 2026, 01:44 AM UTC

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

  3. monitoring Jun 04, 2026, 02:02 AM UTC

    The issue has been successfully mitigated. We will continue to monitor the environment closely and provide updates if any further concerns are identified.

  4. resolved Jun 04, 2026, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

US Region - Dialog GPT Response Latency observed for Customer using MS Azure Open AI

Detected by Pingoru
May 29, 2026, 03:29 PM UTC
Resolved
May 29, 2026, 10:20 PM UTC
Duration
6h 50m
Affected: Bot Uptime
Timeline · 2 updates
  1. investigating May 29, 2026, 03:29 PM UTC

    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.

  2. resolved May 29, 2026, 10:20 PM UTC

    The incident at Azure’s end stands resolved as per https://azure.status.microsoft/en-gb/status. We are resolving this incident as it was created with the intention to make our users and subscribers aware of this issue.

Read the full incident report →

Major May 21, 2026

US Region - AI4Work is experiencing intermittent service disruptions

Detected by Pingoru
May 21, 2026, 08:55 PM UTC
Resolved
May 21, 2026, 09:41 PM UTC
Duration
46m
Affected: AI for Work - USA
Timeline · 3 updates
  1. investigating May 21, 2026, 08:55 PM UTC

    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.

  2. monitoring May 21, 2026, 09:24 PM UTC

    Update - The issue has been mitigated. We are continuing to monitor. Most functionalities should be restored now.

  3. resolved May 21, 2026, 09:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

US Region - Degraded performance of analytics dashboard observed on XO11.

Detected by Pingoru
May 21, 2026, 05:31 PM UTC
Resolved
May 21, 2026, 06:21 PM UTC
Duration
49m
Affected: Bot Builder
Timeline · 4 updates
  1. investigating May 21, 2026, 05:31 PM UTC

    We are currently investigating the issue.

  2. identified May 21, 2026, 05:51 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 21, 2026, 06:03 PM UTC

    A fix has been implemented and we are monitoring the system behaviour.

  4. resolved May 21, 2026, 06:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

US Region - Observing Intermittent timeout errors with the Orchestrator /GPT Module

Detected by Pingoru
May 21, 2026, 01:04 PM UTC
Resolved
May 21, 2026, 01:53 PM UTC
Duration
48m
Affected: Bot Builder
Timeline · 2 updates
  1. identified May 21, 2026, 01:04 PM UTC

    We are currently investigating intermittent timeout errors impacting the Orchestrator / GPT Module. We understand this may be affecting customer experience and appreciate your patience while our teams work to resolve the issue. A fix is currently in progress, and we will continue to share updates as more information becomes available. We apologise for the incovenience caused. Please note: This is not a full outage, and services remain partially operational.

  2. resolved May 21, 2026, 01:53 PM UTC

    We'd like to let you know that the fix has been implemented and validated from our end. The issue is now resolved. We really appreciate your patience.

Read the full incident report →

Minor May 19, 2026

US Region - Analytics dashboard - XO10 and XO11 - Data not loading for May 18th onwards

Detected by Pingoru
May 19, 2026, 08:14 PM UTC
Resolved
May 19, 2026, 08:55 PM UTC
Duration
41m
Affected: Bot Builder
Timeline · 2 updates
  1. investigating May 19, 2026, 08:14 PM UTC

    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.

  2. resolved May 19, 2026, 08:55 PM UTC

    The incident has ben resolved now. We will continuing to monitor the situation at our end.

Read the full incident report →

Major May 18, 2026

US Region - XO10 - Search AI integrations - Partial service disruption

Detected by Pingoru
May 18, 2026, 03:12 PM UTC
Resolved
May 18, 2026, 05:46 PM UTC
Duration
2h 33m
Affected: Application ServiceSearch Service
Timeline · 2 updates
  1. investigating May 18, 2026, 04:47 PM UTC

    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.

  2. resolved May 18, 2026, 05:46 PM UTC

    This incident has now been resolved. Our team will continue to monitor to avoid any further disriptions

Read the full incident report →

Major May 15, 2026

US Region - Degraded performance of analytics dashboard observed across XO10 and XO11.

Detected by Pingoru
May 15, 2026, 03:01 PM UTC
Resolved
May 15, 2026, 06:26 PM UTC
Duration
3h 24m
Affected: Bot Builder
Timeline · 4 updates
  1. investigating May 15, 2026, 03:01 PM UTC

    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.

  2. investigating May 15, 2026, 04:24 PM UTC

    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.

  3. monitoring May 15, 2026, 04:55 PM UTC

    Update - The issue is partially resolved. While the dashboards should be loading now. It may take 2-3 hours more for the bot analytics related dashboards like performance dashboards to load the data. We will keep you updated on the complete resolution of the issue.

  4. resolved May 15, 2026, 06:26 PM UTC

    Update - The issue with the dashboard should be resolved now. We will continue to monitor from our end as well.

Read the full incident report →

Major May 8, 2026

US region - Kore voice gateway - partial service disruption

Detected by Pingoru
May 08, 2026, 12:14 AM UTC
Resolved
May 08, 2026, 02:34 AM UTC
Duration
2h 20m
Affected: Kore IVR
Timeline · 5 updates
  1. investigating May 08, 2026, 12:14 AM UTC

    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.

  2. investigating May 08, 2026, 01:05 AM UTC

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

  3. investigating May 08, 2026, 02:03 AM UTC

    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.

  4. monitoring May 08, 2026, 02:15 AM UTC

    A fix has been implemented and we will continue to monitor the system.

  5. resolved May 08, 2026, 02:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

SaaS US Region - Issues observed with analytics and dashboard sync.

Detected by Pingoru
Apr 28, 2026, 03:48 PM UTC
Resolved
Apr 28, 2026, 06:54 PM UTC
Duration
3h 6m
Affected: Bot Builder
Timeline · 3 updates
  1. identified Apr 28, 2026, 03:48 PM UTC

    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.

  2. identified Apr 28, 2026, 06:11 PM UTC

    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.

  3. resolved Apr 28, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 28, 2026

Recurrence - Issues observed with Azure Open AI may be impacting Kore bots

Detected by Pingoru
Apr 28, 2026, 02:39 PM UTC
Resolved
Apr 28, 2026, 05:03 PM UTC
Duration
2h 24m
Affected: Microsoft Azure ASR/TTSMicrosoft Bot Framework
Timeline · 3 updates
  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 →

Critical April 28, 2026

Major outage on our IND Region with XOCC

Detected by Pingoru
Apr 28, 2026, 05:47 AM UTC
Resolved
Apr 28, 2026, 07:07 AM UTC
Duration
1h 19m
Affected: Kore Agent Desktop
Timeline · 3 updates
  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 →

Major April 27, 2026

Issues observed with Azure Open AI may be impacting Kore bots

Detected by Pingoru
Apr 27, 2026, 10:24 PM UTC
Resolved
Apr 28, 2026, 05:19 AM UTC
Duration
6h 55m
Affected: Microsoft Azure ASR/TTSOpenAI
Timeline · 4 updates
  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 →