pingoru pingoru Korey AI had 5 outages in the last 2 years totaling 9h 18m of downtime, averaging 0.2 incidents per month.
There were 5 Korey AI outages since September 30, 2025 totaling 9h 18m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Korey can't accept new messages at this time. Team is investigating the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
An upstream issue is affecting Korey's communication with WorkOS, resulting in intermittent problems logging in or switching organizations in Korey. We are monitoring the situation.
We are continuing to monitor for any further issues.
This incident has been resolved.
From approximately 3:12am EDT until 5:35am EDT, Korey was unavailable. We identified the cause to be the widespread AWS outage occurring at that time. During that time, StatusPage's administrative interface was also inaccessible, so we are adding a historical incident here to record the event. AWS states that the services which Korey relies on have recovered and we are seeing no further errors in our observability dashboards.
From approximately 3:12am EDT until 5:35am EDT, Korey was unavailable. We identified the cause to be the widespread AWS outage occurring at that time. During that time, StatusPage's administrative interface was also inaccessible, so we are adding a historical incident here to record the event. AWS states that the services which Korey relies on have recovered and we are seeing no further errors in our observability dashboards.
We have detected that some customers are experiencing a loop after signing up, being redirected to create a new Korey organization after already doing so. If you enter this loop, clear all cookies for korey.ai and log in again. Our team is actively working to fix this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.