Is Kore.ai down?
Last checked 4m agoNo incidents right now.
Kore.ai is operational right now. Last checked 4m ago; the most recent incident resolved 3d ago.
Real-time Kore.ai status, recent outages, and incident history — pulled directly from Kore.ai's official status page at https://status.kore.com every 5 minutes. Pingoru tracks 132 Kore.ai services and has captured 115 incidents in the last 90 days (99.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Kore.ai reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- 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.
Latest: 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 success…
-
-
Timeline · 2 updates
- investigating · Jun 11, 2026, 03:58 AM UTC
Dear User, This is to keep you informed that Microsoft Azure has reported an ongoing platform issue affecting the Azure OpenAI Service across multiple regions since 01:02 UTC on 11 June 2026. The issue is impacting the GPT-4.1 Mini (version 2025-04-14) model, where customers may experience: HTTP 5XX errors on LLM requests Request timeouts and intermittent failures Increased response latency and degraded performance Interruptions to applications and workflows dependent on successful model responses Current Status: Microsoft has identified that a sudden increase in request volume on a subset of service endpoints has resulted in capacity constraints, causing request failures and performance degradation. The Azure team is actively investigating, analyzing service telemetry, and scaling resources to stabilize the affected endpoints. Potential Impact: Customers using GPT-4.1 Mini may experience intermittent failures, delayed responses, or unsuccessful completions for chat and prompt requests. We are actively monitoring the situation and coordinating with Microsoft for further updates. Additional information will be shared as it becomes available.
- resolved · Jun 11, 2026, 05:14 AM UTC
Microsoft has confirmed that the issue has been mitigated.
Latest: Microsoft has confirmed that the issue has been mitigated.
-
- Agentic AppToolModel StudioPrompt StudioEvaluationStudioAdminDatasetSearch AI
Timeline · 2 updates
- 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.
- resolved · Jun 11, 2026, 01:02 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Search Service
Timeline · 4 updates
- 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.
- identified · Jun 05, 2026, 06:34 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jun 05, 2026, 06:48 PM UTC
We are monitoring the results.
- resolved · Jun 05, 2026, 07:07 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Agentic Apps
Timeline · 11 updates
- investigating · Jun 05, 2026, 01:53 AM UTC
Dear Users, We are aware of an issue impacting the Agent Platform JP instance and are actively investigating it. Our teams are working to mitigate the issue, and we will share further updates as they become available. Thank you for your patience.
- investigating · Jun 05, 2026, 02:13 AM UTC
Investigation is ongoing. Our teams are actively working to identify the root cause and restore full service functionality. We will provide further updates as progress is made.
- investigating · Jun 05, 2026, 02:36 AM UTC
Our teams continue to investigate the issue and work toward a resolution. We are assessing the underlying cause and will share additional updates as soon as more information becomes available.
- investigating · Jun 05, 2026, 03:19 AM UTC
Our teams are actively analyzing the issue and implementing corrective measures. We will continue to provide updates as the investigation progresses and additional details become available.
- investigating · Jun 05, 2026, 04:01 AM UTC
Our teams are continuing to investigate the issue and work toward a resolution. We will share further updates as more information becomes available and progress is made.
- identified · Jun 05, 2026, 04:35 AM UTC
The issue has been identified and the teams are working on implementing a fix.
- identified · Jun 05, 2026, 06:20 AM UTC
The implementation of the proposed fix is currently in progress. We will provide further updates as work advances and additional details become available.
- identified · Jun 05, 2026, 07:57 AM UTC
The implementation of the proposed fix is currently underway. The service provider is actively working on mitigation efforts to address the issue. We will continue to share updates as progress is made and additional information becomes available.
- identified · Jun 05, 2026, 09:42 AM UTC
Mitigation efforts are currently in progress with the service provider. We will share further updates as soon as additional information becomes available.
- monitoring · Jun 05, 2026, 10:32 AM UTC
The fix has been deployed, and the team is actively monitoring the platform to ensure service stability.
- resolved · Jun 05, 2026, 02:03 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Kore.ai outage history
28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Kore.ai outage history →Or sign up free to get alerts when Kore.ai breaks · 10 free monitors · No credit card
- Started Jun 12, 2026, 09:23 PM UTC · Resolved Jun 11, 2026, 08:40 AM UTC · —
- Azure OpenAI Service Degradation – GPT‑4.1 Mini 5XX Errors and Latency Across Multiple Regions ResolvedStarted Jun 11, 2026, 03:58 AM UTC · Resolved Jun 11, 2026, 05:14 AM UTC · 1h 16m
- Started Jun 11, 2026, 12:26 AM UTC · Resolved Jun 11, 2026, 01:02 AM UTC · 36m
- Started Jun 05, 2026, 05:38 PM UTC · Resolved Jun 05, 2026, 07:07 PM UTC · 1h 28m
- Started Jun 05, 2026, 01:53 AM UTC · Resolved Jun 05, 2026, 02:03 PM UTC · 12h 10m
- Started Jun 04, 2026, 01:30 AM UTC · Resolved Jun 04, 2026, 02:07 AM UTC · 37m
- Started May 29, 2026, 03:29 PM UTC · Resolved May 29, 2026, 10:20 PM UTC · 6h 50m
- Started May 21, 2026, 08:55 PM UTC · Resolved May 21, 2026, 09:41 PM UTC · 46m