Reducto Outage History

Reducto is up right now

Pingoru has recorded 51 incidents for Reducto: 46 in the last 12 months and 11 in the last 90 days.

Source: status.reducto.ai

51incidents recorded
46last 12 months
11last 90 days
3 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Reducto in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202641 of 720 (0%)
May 202667 of 744 (1%)
June 2026914 of 720 (2%)
July 202627 of 744 (1%)
August 202643 of 744 (0%)
September 2026418 of 720 (2%)
October 202623 of 592 (0%)

Incidents, newest first

Minor May 6, 2026 Rolling deploy caused transient errors 19m Parsing, Studio, Extraction

Started May 06, 2026, 09:41 PM UTC· resolved May 06, 2026, 10:00 PM UTC

  1. identified May 06, 2026, 09:41 PM UTC

    Rolling deployment started. We started observing transient failures during the deploy process.

  2. resolved May 06, 2026, 10:00 PM UTC

    Changes were rolled back and error rate dropped to normal rates.

Read the full incident report →

Minor April 8, 2026 Partially degraded Studio inferences 9m Studio

Started Apr 08, 2026, 06:18 PM UTC· resolved Apr 08, 2026, 06:28 PM UTC

  1. identified Apr 08, 2026, 06:18 PM UTC

    We've identified an issue that is impacting fetching inference results on Studio.

  2. monitoring Apr 08, 2026, 06:22 PM UTC

    We've deployed a fix for runs and are continuing to monitor.

  3. resolved Apr 08, 2026, 06:28 PM UTC

    All Studio runs should now be successful.

Read the full incident report →

Minor April 8, 2026 Degraded Performance on a small percentage of jobs –

Started Apr 08, 2026, 04:00 AM UTC· resolved Apr 08, 2026, 04:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 4, 2026 Backend Vendor reporting major outage 1h 2m Parsing, Studio, Extraction

Started Mar 04, 2026, 05:33 PM UTC· resolved Mar 04, 2026, 06:36 PM UTC

  1. monitoring Mar 04, 2026, 05:33 PM UTC

    Our Backend vendor is reporting high error rates, impacting our Studio experience. We are monitoring the situation, and will update when resolved

  2. monitoring Mar 04, 2026, 05:42 PM UTC

    /pipeline invocation and Studio severely impacted - Backend vendor reporting major outage

  3. resolved Mar 04, 2026, 06:36 PM UTC

    backend incident no longer affecting product experience or /pipeline invocation

Read the full incident report →

Minor February 13, 2026 temporary outage 2m

Started Feb 13, 2026, 10:38 PM UTC· resolved Feb 13, 2026, 10:40 PM UTC

  1. monitoring Feb 13, 2026, 10:38 PM UTC

    a portion of jobs between 14:27-14:32 PST failed. All services are operational now

  2. resolved Feb 13, 2026, 10:40 PM UTC

    all services are operational now

Read the full incident report →

Minor February 12, 2026 degraded latency 3h 14m Parsing, Extraction

Started Feb 12, 2026, 05:17 PM UTC· resolved Feb 12, 2026, 08:31 PM UTC

  1. investigating Feb 12, 2026, 05:17 PM UTC

    increased latency, unknown cause for now

  2. monitoring Feb 12, 2026, 06:47 PM UTC

    We are monitoring the resolution.

  3. resolved Feb 12, 2026, 08:31 PM UTC

    We've root caused and resolved database issues. Services are fully operational.

Read the full incident report →

Minor January 30, 2026 elevated timeouts on a subset of jobs 52m Parsing, Extraction

Started Jan 30, 2026, 10:07 PM UTC· resolved Jan 30, 2026, 11:00 PM UTC

  1. investigating Jan 30, 2026, 10:07 PM UTC

    The team is investigating timeouts

  2. monitoring Jan 30, 2026, 10:48 PM UTC

    All services back up, the team will continue monitoring

  3. resolved Jan 30, 2026, 11:00 PM UTC

    All services back to normal

Read the full incident report →

Minor January 30, 2026 Investigating elevated failure rates on the API 17h 5m Parsing, Extraction

Started Jan 30, 2026, 03:04 AM UTC· resolved Jan 30, 2026, 08:10 PM UTC

  1. investigating Jan 30, 2026, 03:04 AM UTC

    Investigating elevated failure rates.

  2. monitoring Jan 30, 2026, 03:13 AM UTC

    We've identified the issue and deployed a fix. We are monitoring to ensure systems are healthy.

  3. resolved Jan 30, 2026, 08:10 PM UTC

    We haven't observed any additional failures.

Read the full incident report →

Minor January 23, 2026 Investigating elevated parsing latencies 3h 40m

Started Jan 23, 2026, 03:35 PM UTC· resolved Jan 23, 2026, 07:15 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major January 16, 2026 Increased Parse Failures –

Started Jan 16, 2026, 05:54 PM UTC· resolved Jan 16, 2026, 05:54 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor December 17, 2025 Investigating elevated 500 errors. 1d 14h

Started Dec 17, 2025, 04:45 PM UTC· resolved Dec 19, 2025, 07:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major November 19, 2025 Investigating database overload causing jobs to fail 3h 50m

Started Nov 19, 2025, 06:04 PM UTC· resolved Nov 19, 2025, 09:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor November 18, 2025 Increased job failures due to database connection timeouts 28m

Started Nov 18, 2025, 09:36 PM UTC· resolved Nov 18, 2025, 10:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 24, 2025 Investigating degraded performance 42m

Started Oct 24, 2025, 08:34 PM UTC· resolved Oct 24, 2025, 09:16 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 20, 2025 Elevated 504 Errors 1h 21m

Started Oct 20, 2025, 05:08 PM UTC· resolved Oct 20, 2025, 06:30 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 20, 2025 AWS Outage 54m

Started Oct 20, 2025, 09:05 AM UTC· resolved Oct 20, 2025, 10:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 14, 2025 Small fraction of jobs errored to do read-only issue with DB connection –

Started Oct 14, 2025, 04:09 AM UTC· resolved Oct 14, 2025, 04:09 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major October 11, 2025 Some jobs failing to queue –

Started Oct 11, 2025, 08:57 PM UTC· resolved Oct 11, 2025, 08:57 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →