Is Reducto down?
Last checked 4m agoNo incidents right now.
Reducto is operational right now. Last checked 4m ago; the most recent incident resolved 4d 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 5 Reducto services and has captured 12 incidents in the last 90 days (97.11% uptime). Get email, Slack, Discord, or webhook alerts the moment Reducto reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Splitting
Timeline · 2 updates
- investigating · Sep 09, 2026, 11:22 PM UTC
Status: Investigating Deep Split experienced partial degradation beginning at 16:22 PDT on September 9. Impact was limited to Deep Split requests. Affected components Splitting (Degraded performance)
- resolved · Sep 09, 2026, 11:33 PM UTC
Status: Resolved The change was rolled back at 16:33 PDT, restoring normal Deep Split operation. The degradation lasted approximately 11 minutes and was limited to Deep Split requests. Affected components Splitting (Operational)
Latest: Status: Resolved The change was rolled back at 16:33 PDT, restoring normal Deep Split operation. The degradation lasted approximately 11 minutes and was limited to Deep Split reque…
-
- Extraction
Timeline · 3 updates
- identified · Aug 18, 2026, 04:13 PM UTC
Status: Identified Extract requests that use citations or confidence scores are seeing elevated latency. The cause is an issue with one of our GPU clusters. Affected components Extraction (Degraded performance)
- monitoring · Aug 18, 2026, 04:13 PM UTC
Status: Monitoring We have rolled out a fix and latency has returned to normal. We are monitoring to confirm the issue is fully resolved.
- resolved · Aug 18, 2026, 06:22 PM UTC
Status: Resolved This is resolved. The GPU cluster issue has been fixed and Extract latency, including requests that use citations or confidence scores, has returned to normal. We confirmed full recovery. Thank you for your patience. Affected components Extraction (Operational)
Latest: Status: Resolved This is resolved. The GPU cluster issue has been fixed and Extract latency, including requests that use citations or confidence scores, has returned to normal. We …
-
- Parsing
Timeline · 2 updates
- identified · Aug 18, 2026, 04:52 PM UTC
Status: Identified Elevated latency for parse, due to an issue with one of our gpu clusters. We've identified the problem and are actively fixing it. Affected components Parsing (Degraded performance)
- resolved · Aug 18, 2026, 06:22 PM UTC
Status: Resolved This is resolved. The GPU cluster issue has been fixed and parse latency has returned to normal. We confirmed recovery across the fleet. Thank you for your patience. Affected components Parsing (Operational)
Latest: Status: Resolved This is resolved. The GPU cluster issue has been fixed and parse latency has returned to normal. We confirmed recovery across the fleet. Thank you for your patienc…
-
- Parsing
Timeline · 2 updates
- investigating · Aug 13, 2026, 05:40 PM UTC
Status: Investigating We are investigating elevated latency on the parse API. Some parse jobs take longer than normal to complete. Affected components Parsing (Degraded performance)
- resolved · Aug 13, 2026, 06:10 PM UTC
Status: Resolved We corrected a misconfiguration in our GPU inference fleet. Parse latency returned to normal levels. Affected components Parsing (Operational)
Latest: Status: Resolved We corrected a misconfiguration in our GPU inference fleet. Parse latency returned to normal levels. Affected components Parsing (Operational)
-
- ExtractionSplitting
Timeline · 2 updates
- investigating · Aug 13, 2026, 04:31 PM UTC
Status: Investigating We are seeing elevated latency on Extract and Split requests. Requests are completing, but slower than normal. We are investigating and will post an update shortly. Affected components Extraction (Degraded performance) Splitting (Degraded performance)
- resolved · Aug 13, 2026, 04:54 PM UTC
Status: Resolved This is resolved. The cause was a Redis connection issue, which we have fixed. Extract and Split latency is back to normal. Thank you for your patience. Affected components Extraction (Operational) Splitting (Operational)
Latest: Status: Resolved This is resolved. The cause was a Redis connection issue, which we have fixed. Extract and Split latency is back to normal. Thank you for your patience. Affected c…
-
See the full Reducto outage history
7 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
- Partial degradation of Deep Split ResolvedStarted Sep 09, 2026, 11:33 PM UTC · Resolved Sep 09, 2026, 11:33 PM UTC · —
- Started Aug 18, 2026, 06:22 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC · —
- Elevated latency for /parse ResolvedStarted Aug 18, 2026, 06:22 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC · —
- Elevated parse latency ResolvedStarted Aug 13, 2026, 06:10 PM UTC · Resolved Aug 13, 2026, 06:10 PM UTC · —
- Degraded latency for Extract ResolvedStarted Aug 13, 2026, 04:54 PM UTC · Resolved Aug 13, 2026, 04:54 PM UTC · —
- Investigating latency in EU ResolvedStarted Jul 28, 2026, 03:18 PM UTC · Resolved Jul 28, 2026, 03:18 PM UTC · —
- Started Jul 23, 2026, 05:43 PM UTC · Resolved Jul 23, 2026, 05:43 PM UTC · —
- Started Jun 26, 2026, 04:01 AM UTC · Resolved Jun 26, 2026, 04:01 AM UTC · —