Is Reducto down?
Last checked 2m agoNo incidents right now.
Reducto is operational right now. Last checked 2m ago; the most recent incident resolved 30d ago.
Real-time Reducto status, recent outages, and incident history: pulled directly from Reducto's official status page at status.reducto.ai every 5 minutes. Pingoru tracks 5 Reducto services and has captured 10 incidents in the last 90 days (98.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Reducto reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Parsing
Timeline · 2 updates
- investigating · Oct 01, 2026, 09:13 PM UTC
Status: Investigating We are investigating degraded performance on the Parse API in the EU region (eu.platform.reducto.ai). Only the EU region is affected. Affected components Parsing (Degraded performance)
- resolved · Oct 01, 2026, 10:10 PM UTC
Status: Resolved The Parse API in the EU region returned no errors after 21:18 UTC. This incident is resolved. Affected components Parsing (Operational)
Latest: Status: Resolved The Parse API in the EU region returned no errors after 21:18 UTC. This incident is resolved. Affected components Parsing (Operational)
-
- Parsing
Timeline · 3 updates
- investigating · Oct 01, 2026, 07:07 PM UTC
Status: Investigating We are investigating degraded performance on the Parse API. Affected components Parsing (Degraded performance)
- monitoring · Oct 01, 2026, 08:02 PM UTC
Status: Monitoring An outage of our OCR service caused the degraded performance on the Parse API. The OCR service has recovered. We are monitoring the results. Affected components Parsing (Operational)
- resolved · Oct 01, 2026, 09:00 PM UTC
Status: Resolved The Parse API is fully recovered. This incident is resolved. Affected components Parsing (Operational)
Latest: Status: Resolved The Parse API is fully recovered. This incident is resolved. Affected components Parsing (Operational)
-
- Parsing
Timeline · 4 updates
- investigating · Sep 28, 2026, 03:05 AM UTC
Status: Investigating Parse requests are degraded. Only the /parse endpoint is affected. Extract, Split, and Edit are operating normally. We are investigating. Affected components Parsing (Degraded performance)
- identified · Sep 28, 2026, 03:22 AM UTC
Status: Identified Parse latency is degraded because of an issue with our GPU clusters. Our engineers are working on a fix. Only the /parse endpoint is affected. Affected components Parsing (Degraded performance)
- monitoring · Sep 28, 2026, 03:35 AM UTC
Status: Monitoring The GPU clusters are recovered, and Parse latency is back to normal. We are monitoring the results. Affected components Parsing (Operational)
- resolved · Sep 28, 2026, 08:09 PM UTC
Status: Resolved This incident is resolved. Parse latency has been normal since 8:35 PM PDT on September 27.
Latest: Status: Resolved This incident is resolved. Parse latency has been normal since 8:35 PM PDT on September 27.
-
-
Timeline · 1 update
- resolved · Sep 16, 2026, 02:51 AM UTC
Status: Resolved This is resolved. Parse requests with embed_pdf_metadata set to true are operating normally.
Latest: Status: Resolved This is resolved. Parse requests with embed_pdf_metadata set to true are operating normally.
-
- Parsing
Timeline · 2 updates
- investigating · Sep 16, 2026, 02:28 AM UTC
Status: Investigating Parse requests with embed_pdf_metadata set to true are degraded. Other Parse requests are unaffected. We are investigating. Affected components Parsing (Degraded performance)
- resolved · Sep 16, 2026, 02:48 AM UTC
Status: Resolved This is resolved. Parse requests with embed_pdf_metadata set to true are operating normally. Affected components Parsing (Operational)
Latest: Status: Resolved This is resolved. Parse requests with embed_pdf_metadata set to true are operating normally. Affected components Parsing (Operational)
-
See the full Reducto outage history
5 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
Incident record
Since April 2026 · incident.io · 5 components checked every 5 minutesThe longest incident in the last year, Investigating elevated 500 errors. on December 17, 2025, ran for 38 hours. 2 maintenance windows announced in the same period.
Most affected components, last 12 months
- Parsing26
- Extraction19
- Studio8
- Splitting2
Latest incidents
- Degraded performance on Parse API in the EU region
Status: Investigating We are investigating degraded performance on the Parse API in the EU region (eu.platform.reducto.ai). Only the EU region is affected.…
- Degraded performance on Parse API
Status: Investigating We are investigating degraded performance on the Parse API. Affected components Parsing (Degraded performance)
- Partial degradation of Parse
Status: Investigating Parse requests are degraded. Only the /parse endpoint is affected. Extract, Split, and Edit are operating normally. We are investigating.…
- Started Oct 01, 2026, 09:13 PM UTC · Resolved Oct 01, 2026, 10:10 PM UTC · 56m
- Degraded performance on Parse API ResolvedStarted Oct 01, 2026, 07:07 PM UTC · Resolved Oct 01, 2026, 09:00 PM UTC · 1h 52m
- Partial degradation of Parse ResolvedStarted Sep 28, 2026, 03:05 AM UTC · Resolved Sep 28, 2026, 08:09 PM UTC · 17h 3m
- Started Sep 16, 2026, 02:51 AM UTC · Resolved Sep 16, 2026, 02:51 AM UTC · –
- Started Sep 16, 2026, 02:28 AM UTC · Resolved Sep 16, 2026, 02:48 AM UTC · 20m
- Partial degradation of Deep Split ResolvedStarted Sep 09, 2026, 11:22 PM UTC · Resolved Sep 09, 2026, 11:33 PM UTC · 11m
- Elevated latency for /parse ResolvedStarted Aug 18, 2026, 04:52 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC · 1h 29m
- Started Aug 18, 2026, 04:13 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC · 2h 8m