Degraded Performance in Orchestrate
Incident Lifecycle
Incident Timeline
Identified
At 04:00 UTC on April 9, 2026, degraded performance was observed in the Orchestrate service due to increased system load. The issue was identified as being caused by a retry mechanism repeatedly processing failed jobs. These failures stemmed from oversized payloads (~6 MB) generated in custom actions, which exceeded Kubernetes API server limits, leading to continuous retries and added strain on the system.
Apr 10, 2026 at 6:28 AM UTC
Was your business affected by this SuperAnnotate AI outage?
Set up instant alerts for SuperAnnotate AI — be the first to know about outages via email, Slack, Teams, or Discord.