New Multi-region uptime checks and custom-domain status pages

SuperAnnotate AI Outage History

Daily provider-status observations and published incident history for SuperAnnotate AI.

Operational

SuperAnnotate AI is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow SuperAnnotate AI for future changes.

100% of 37 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

2 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

May 2026
Issue Opening PDF, Markdown, and Custom Components in Multimodal Project
major Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and fix is being implemented.
investigating
We’re currently experiencing issues opening items with PDF, Markdown, and some custom components in the Multimodal project. We’re investigating the problem and working on a fix.
April 2026
Degraded Performance in Orchestrate
Source not attested
Last archived state: resolved
View archived record details
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.