Reducto incident

Degraded Performance on a small percentage of jobs

Minor Resolved View vendor source →
Started
Apr 08, 2026, 04:00 AM UTC
Resolved
Apr 08, 2026, 04:00 AM UTC
Duration
Detected by Pingoru
Apr 08, 2026, 04:00 AM UTC

Affected components

ParsingStudioExtraction

Update timeline

  1. investigating Apr 08, 2026, 03:21 AM UTC

    Status: Investigating A small percentage of jobs errored out due to elevated errors with our inference services Affected components Parsing (Degraded performance) Extraction (Degraded performance) Studio (Operational)

  2. identified Apr 08, 2026, 03:55 AM UTC

    Status: Identified The root cause was identified and the inference change was reverted. Affected components Parsing (Degraded performance) Extraction (Degraded performance) Studio (Operational)

  3. monitoring Apr 08, 2026, 03:57 AM UTC

    Status: Monitoring An updated deployment has restored service for all new jobs. Affected components Studio (Operational) Parsing (Degraded performance) Extraction (Degraded performance)

  4. resolved Apr 08, 2026, 04:00 AM UTC

    Status: Resolved All inference services restored. New jobs will continue to succeed. Affected components Parsing (Operational) Extraction (Operational) Studio (Operational)

Looking to track Reducto downtime and outages?

Pingoru polls Reducto's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Reducto reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Reducto alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Reducto for free

5 free monitors · No credit card required