Is Reducto down?

Last checked just now
Current status
Reducto is up

No incidents right now.

Official status page: https://status.reducto.ai · Polled every 5 minutes · 3 components tracked

Reducto is operational right now. Last checked just now; the most recent incident resolved 2d ago.

Real-time Reducto status, recent outages, and incident history — pulled directly from Reducto's official status page at https://status.reducto.ai every 5 minutes. Pingoru tracks 3 Reducto services and has captured 15 incidents in the last 90 days (91.48% uptime). Get email, Slack, Discord, or webhook alerts the moment Reducto reports a new incident — free for 5 monitors, no credit card.

Users who monitor Reducto also follow these Legal services: DocuSign PandaDoc Conga Contracts Yousign MyCase Revenera SignRequest Clio Smokeball LinkSquares View all 6,000+ providers
Reducto uptime 91.48% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 11, 2026, 08:47 PM UTC · Resolved Jun 11, 2026, 08:47 PM UTC
    Parsing
    Timeline · 4 updates
    • investigating · Jun 11, 2026, 08:43 PM UTC

      Status: Investigating /parse with config use_checkboxes set to true are failing Affected components Parsing (Degraded performance)

    • identified · Jun 11, 2026, 08:43 PM UTC

      Status: Identified identified and reverting deploy Affected components Parsing (Degraded performance)

    • monitoring · Jun 11, 2026, 08:44 PM UTC

      Status: Monitoring monitoring fix Affected components Parsing (Degraded performance)

    • resolved · Jun 11, 2026, 08:47 PM UTC

      Status: Resolved recovered - a portion of parse requests from 1330-1343 PST failed, all operational now Affected components Parsing (Operational)

    Latest: Status: Resolved recovered - a portion of parse requests from 1330-1343 PST failed, all operational now Affected components Parsing (Operational)

  2. Resolved
    Started Jun 09, 2026, 11:41 PM UTC · Resolved Jun 09, 2026, 11:41 PM UTC
    Parsing
    Timeline · 3 updates
    • investigating · Jun 09, 2026, 10:10 PM UTC

      Status: Investigating Requests that set ocr_system = legacy in the v3 config, or ocr_system = highres in the v2 config are experiencing increased latency / transient errors Affected components Parsing (Degraded performance)

    • monitoring · Jun 09, 2026, 10:33 PM UTC

      Status: Monitoring Latency back to normal for legacy ocr service, monitoring Affected components Parsing (Degraded performance)

    • resolved · Jun 09, 2026, 11:41 PM UTC

      Status: Resolved All services functional Affected components Parsing (Operational)

    Latest: Status: Resolved All services functional Affected components Parsing (Operational)

  3. Resolved
    Started Jun 05, 2026, 03:25 PM UTC · Resolved Jun 05, 2026, 03:25 PM UTC
    ParsingStudioExtraction
    Timeline · 2 updates
    • identified · Jun 05, 2026, 02:24 PM UTC

      Status: Identified Degraded performance due to queue saturation on US processing. Affected components Parsing (Degraded performance) Extraction (Degraded performance) Studio (Operational)

    • resolved · Jun 05, 2026, 03:25 PM UTC

      Status: Resolved Resolved queue saturation incident. Affected components Parsing (Operational) Extraction (Operational) Studio (Operational)

    Latest: Status: Resolved Resolved queue saturation incident. Affected components Parsing (Operational) Extraction (Operational) Studio (Operational)

  4. Resolved
    Started Jun 03, 2026, 03:53 PM UTC · Resolved Jun 03, 2026, 03:53 PM UTC
    ParsingExtraction
    Timeline · 5 updates
    • 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)

    Latest: Status: Resolved All endpoints should now be working as expected. All upstream provider issues are now resolved. Affected components Extraction (Operational) Parsing (Operational)

  5. Resolved
    Started May 21, 2026, 05:15 PM UTC · Resolved May 21, 2026, 05:15 PM UTC
    ParsingStudioExtraction
    Timeline · 2 updates
    • identified · May 21, 2026, 05:07 PM UTC

      Status: Identified Investigating elevated failure rates. Affected components Parsing (Degraded performance) Extraction (Degraded performance) Studio (Operational)

    • resolved · May 21, 2026, 05:15 PM UTC

      Status: Resolved Fully mitigated. Affected components Parsing (Operational) Extraction (Operational) Studio (Operational)

    Latest: Status: Resolved Fully mitigated. Affected components Parsing (Operational) Extraction (Operational) Studio (Operational)

See the full Reducto outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Reducto outage history →

Or sign up free to get alerts when Reducto breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →