Kore.ai incident
Investigating issues with Agent Platform on the JP Instance.
Kore.ai experienced a critical incident on June 5, 2026 affecting Agentic Apps, lasting 12h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.