Reducto incident
Elevated failure rate with upstream inference provider
Reducto experienced a minor incident on June 3, 2026 affecting Parsing and Extraction, lasting 2h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 03, 2026, 01:12 PM UTC
Status: Investigating We’re seeing an increase in failures and latency. Investigating now. Affected components Parsing (Degraded performance) Extraction (Degraded performance)
- identified Jun 03, 2026, 01:32 PM UTC
Status: Identified We identified an issue with our GPU cloud subprocessor. We have engaged our emergency fallback inference system and are seeing initial recovery albeit with degraded performance. Affected components Parsing (Degraded performance) Extraction (Degraded performance)
- monitoring Jun 03, 2026, 03:40 PM UTC
Status: Monitoring Inference provider fallbacks were put in place for short-term mitigation. We're seeing complete recovery across all endpoints Affected components Extraction (Degraded performance) Parsing (Degraded performance)
- resolved Jun 03, 2026, 03:53 PM UTC
Status: Resolved All endpoints should now be working as expected. All upstream provider issues are now resolved. Affected components Parsing (Operational) Extraction (Operational)
- resolved Jun 03, 2026, 03:53 PM UTC
Status: Resolved All endpoints should now be working as expected. All upstream provider issues are now resolved. Affected components Extraction (Operational) Parsing (Operational)