Is Reducto down?

Last checked 8m ago
Current status
Reducto is up

No incidents right now.

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

Reducto is operational right now. Last checked 8m ago; 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 5 Reducto services and has captured 13 incidents in the last 90 days (97.33% 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 97.33% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 16, 2026, 02:51 AM UTC · Resolved Sep 16, 2026, 02:51 AM UTC
    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.

  2. Resolved
    Started Sep 16, 2026, 02:48 AM UTC · Resolved Sep 16, 2026, 02:48 AM UTC
    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)

  3. Resolved
    Started Sep 09, 2026, 11:33 PM UTC · Resolved Sep 09, 2026, 11:33 PM UTC
    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…

  4. Resolved
    Started Aug 18, 2026, 06:22 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC
    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 …

  5. Resolved
    Started Aug 18, 2026, 06:22 PM UTC · Resolved Aug 18, 2026, 06:22 PM UTC
    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…

See the full Reducto outage history

8 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 · 13 incidents View full outage history →