S
Outage recap · SuperAnnotate

SuperAnnotate outage — April 9, 2026

On April 9, 2026, SuperAnnotate had a reported incident on SuperAnnotate's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded Performance in Orchestrate

none
Started
Apr 9, 12:00 AM EDT
Resolved
Apr 9, 1:15 AM EDT
Duration
1h 15m

SuperAnnotate's updates (2)

  1. identified · Apr 9, 12:00 AM EDT

    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.

  2. resolved · Apr 9, 1:15 AM EDT

    By 05:15 UTC, immediate mitigation was completed by scaling up Orchestrate service resources, stabilizing the system and stopping further degradation. Additional safeguards, including payload size limits and an upcoming SDK fix, were prepared to prevent recurrence.

Updates are SuperAnnotate's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with SuperAnnotate. This recap summarizes incidents published on SuperAnnotate's official status page.