Kore.ai Outage History

OpenAI has mitigated the issue affecting ChatGPT conversations and is monitoring recovery. We do not see any further errors being reported by OpenAI for this issue.

Status: Resolved Impact Severity: Minor / Service Degradation Impact Window: 10:28 AM EST – 10:33 AM EST Incident Description: Between 10:28 AM EST and 10:33 AM EST today, a few of our customers using AWS Transcribe (ASR) automated voice interactions experienced a brief service disruption affecting Speech-to-Text processing. During this short window, a subset of callers utilizing automated voice navigation experienced transcription processing errors. Root Cause: The issue originated from a transient disruption with our primary third-party Speech-to-Text service provider (AWS Transcribe). The provider's platform has since stabilized, and service was fully restored without internal system modifications required. Current Status & Resolution: System telemetry indicates that voice transcription processing returned to normal parameters at 10:33 AM EST. Our continued monitoring did not indicate any recurrence of this issue.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This is to keep the Kore users updated that an incident at OpenAI may have impacted your operations on Kore apps. This incident reportedly caused degraded performance of several Codex and OpenAI components. As notified by OpenAI, incident started at Sep 3, 2026, 10:43 AM EST and was resolved around Sep 3, 2026, 12:55 PM EST. For further details, please see https://status.openai.com/incidents/01M1KWEDH417T2CF44YYHZDFCR

This incident has been resolved.

On August 29, 2026, at approximately 2:30 PM IST / 4:00 AM EST, our US SaaS customers may have experienced difficulty accessing the service or receiving Dialog GPT response chunks following the UXO/XO11 version 11.28.0 release. Our team promptly identified the issue and worked to restore normal service. We apologize for any inconvenience this may have caused.

The incident has been resolved. We will continue to monitor the system’s behavior to ensure ongoing stability.

Dear User, We observed intermittent bot response issues and performance degradation affecting our US Azure West instance between 6:10 PM and 6:50 PM IST (8:40 AM and 9:20 AM ET). The issue was identified and has been resolved. Service performance has returned to normal. We apologize for any inconvenience caused and appreciate your patience.

Resolved – Intermittent Call Drops Between 9:44 PM IST (12:14 PM EST) and 10:31 PM IST (1:01 PM EST) on August 18, 2026, we observed intermittent call drops associated with 487 – Request Terminated errors. The issue may have affected a subset of bots during this period. Our teams promptly investigated and resolved the issue. No further occurrences have been observed since 10:31 PM IST (1:01 PM EST). We apologize for any inconvenience caused. We are continuing to monitor the platform to ensure stability and will provide further updates if necessary.

This incident has been resolved.

This incident has been resolved.

We identified an issue affecting the JP region, where a few of customers experienced difficulties logging in to XOCC. A fix has been implemented, and the service has been restored. We are currently monitoring the environment to ensure continued stability. We sincerely apologize for the inconvenience caused and appreciate your patience

This incident has been resolved.

Dear User, We would like to inform you that we are aware of an ongoing incident impacting the Azure West US region. Customers using Azure AI Speech Services hosted in the US West region may experience intermittent connectivity issues, increased latency, or difficulties accessing the services. The issue started at 14:44 UTC on 23 July 2026. The impact may include connectivity failures and degraded performance for services hosted within the Azure West US region. Microsoft has identified a potential trigger and is actively working on mitigation by isolating impacted devices and redirecting traffic to healthier infrastructure. Their teams are closely monitoring the recovery progress and assessing customer impact. For the latest updates, please refer to the Microsoft Azure Service Health Status page: https://azure.status.microsoft/en-gb/status

The issue is now resolved. Thank You for your patience.

We are notifying you that our Developer Portal (https://developer.kore.ai) experienced a service disruption on 16 July 2026 from 8:30 AM IST to 9:27 AM IST, lasting approximately 56 minutes. During this period, the Developer Portal, including access to product documentation, was unavailable. The service has since been fully restored, and the Developer Portal is now operating normally. We sincerely apologize for the inconvenience this may have caused and appreciate your patience and understanding.

We observed intermittent performance degradation on the UAE Instance between 07:39 PM IST and 08:06 PM IST (06:09 PM GST and 06:36 PM GST, UAE Time). The issue was identified by our teams and mitigation actions have been applied. Service performance has since stabilized, and we continue to monitor the environment closely to ensure normal operations. We apologize for any inconvenience caused and will provide further updates if necessary.

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.

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.

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

This incident has been resolved.