SuperAnnotate AI Outage History
11 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded SuperAnnotate AI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 8, 2026 | Elevated Response TimesBetween 11:00–11:30 UTC, we experienced elevated load that may have caused intermittent slowness on the platform. This has been resolved and all systems are operating normally. | 0 min | Resolved |
| May 7, 2026 | Issue Opening PDF, Markdown, and Custom Components in Multimodal ProjectDuring the recent release, an issue occurred in the CDN distribution that serves external frontend libraries. As a result, requests to load certain static assets \(e.g., `pdfjs-express/8.7.2/webviewer.min.js`\) returned… | 1h 39m | Resolved |
| Apr 9, 2026 | Degraded Performance in OrchestrateBy 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… | 1h 14m | Resolved |
| Mar 31, 2026 | Degraded PerformanceBetween 10:00 UTC and 12:30 UTC, a subset of requests failed due to reaching the database resource limit \(max\_prepared\_stmt\_count\) under sustained load. The issue has been resolved by increasing the available… | 2h 29m | Resolved |
| Mar 26, 2026 | Increased Job Failures in OrchestrateThe Kubernetes network issue has been fixed, and job processing is back to normal. | 2h 19m | Resolved |
| Mar 26, 2026 | Invitation Emails Not Being SentService has been restored and is operating normally. We are continuing to investigate the root cause and assess the overall impact. | 1h 2m | Resolved |
| Mar 19, 2026 | Orchestrate: Action Creation UnavailableAction Creation was temporarily unavailable for all customers due to disk space exhaustion. Timeline: Start: 01:13 UTC+4 Resolved: 02:37 UTC+4 Resolution: Disk capacity and IOPS were increased, restoring the service. | 0 min | Resolved |
| Feb 23, 2026 | Orchestrate – Item event-triggered actions are not firing, Work Management - workload number of assignments are not updated.### **Summary** On February 23 2026, a production Kafka Connect connector responsible for streaming MySQL binlog events temporarily stopped processing new events while remaining in a RUNNING state. Because the… | 40 min | Resolved |
| Feb 17, 2026 | Performance Issue on the ApplicationBetween 06:43 and 10:40 UTC, we experienced elevated platform load that impacted some services. Our team increased service limits and applied adjustments to stabilize the system. A fix was deployed at 10:40 UTC, after… | -15853 min | Resolved |
| Feb 16, 2026 | Outage on Editors### **Summary** On February 16 2026, a CloudFront configuration update introduced request-processing logic at the viewer-request stage for the production distribution. During deployment, a timing overlap occurred… | 0 min | Resolved |
| Feb 5, 2026 | Downtime Due to Post-Release SyncThere was an outage on our platform connected to post-release synchronization failure. This occured around 10:30 UTC and lasted about 15 minutes. The team identified and resolved the issue, and everything is now up and… | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next SuperAnnotate AI incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This SuperAnnotate AI Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SuperAnnotate AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single SuperAnnotate AI outage in this window ran 2h 29m, against a mean recovery of 56 min. If you depend on SuperAnnotate AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.