Parseur Outage History

Parseur is up right now

Pingoru has recorded 20 incidents for Parseur: 4 in the last 12 months and 1 in the last 90 days.

Source: status.parseur.com

20incidents recorded
4last 12 months
1last 90 days
28 hourstypical duration

Incidents, newest first

Minor September 7, 2026 Intermittent uploading difficulties 1h 59m Parseur app, Parseur API

Started Sep 07, 2026, 12:09 PM UTC· resolved Sep 07, 2026, 02:08 PM UTC

  1. monitoring Sep 07, 2026, 12:09 PM UTC

    We've implemented a fix and are monitoring - queued documents are processing properly now.

  2. resolved Sep 07, 2026, 02:08 PM UTC

    All queued documents have been processed and this issue has been resolved.

Read the full incident report →

Minor May 28, 2026 Delayed document processing 1d 7h

Started May 28, 2026, 02:25 PM UTC· resolved May 29, 2026, 10:06 PM UTC

  1. investigating May 28, 2026, 02:17 PM UTC

    We are currently observing increased delays in processing due to heavy server load and are actively working toward a solution. Documents will process once this queue has subsided.

  2. investigating May 28, 2026, 04:32 PM UTC

    We are still investigating and trying to increase server capacity.

  3. monitoring May 29, 2026, 06:09 AM UTC

    The backlog has been fully cleared, and document processing is operating normally. While our peak processing capacity remains temporarily limited by our AI provider, we have requested additional capacity and are awaiting approval. We are actively monitoring the situation.

  4. resolved May 29, 2026, 10:06 PM UTC

    We are still awaiting approval for increased capacity. We have not had any significant delays in processing today, however, so this incident is being marked as resolved.

Read the full incident report →

Minor March 17, 2026 Delayed document deletion 2d 22h

Started Mar 17, 2026, 08:10 AM UTC· resolved Mar 20, 2026, 06:14 AM UTC

  1. identified Mar 17, 2026, 08:01 AM UTC

    We have resolved an issue that delayed our automated document deletion system. The deletion process has resumed, but it may take a few hours for the system to process the backlog and fully catch up to your configured retention settings.

  2. monitoring Mar 18, 2026, 08:00 AM UTC

    We are monitoring the resolution of the issue and will keep you updated once it is resolved.

  3. resolved Mar 20, 2026, 06:14 AM UTC

    Incident is resolved, retention is now applied in real time.

Read the full incident report →

Minor January 23, 2026 Intermittent document processing errors with AI Engine v2 8h 40m Parseur API

Started Jan 23, 2026, 05:56 AM UTC· resolved Jan 23, 2026, 02:37 PM UTC

  1. investigating Jan 23, 2026, 05:53 AM UTC

    We’ve seen an increase in intermittent processing errors when processing documents with AI Engine v2. Our team is actively investigating. In the meantime, if you see documents failing with “Process Failed (AI)”, we recommend one of the following workarounds: - Retry later: manually reprocess the affected documents after a short delay (the issue is intermittent and retries often succeed). - Switch engines: move to the newly released AI Engine v2.5, which should reduce or eliminate these errors. We’ll share an update as soon as we have more information.

  2. identified Jan 23, 2026, 07:05 AM UTC

    We’ve found the source of the problem and are currently developing a fix.

  3. monitoring Jan 23, 2026, 07:54 AM UTC

    We’ve rolled out an update to mitigate document processing failures by improving our existing retry mechanism. With this improvement, when a processing attempt fails, the system will now retry a few times more effectively to help ensure the document completes successfully. Most documents should eventually process successfully, though retries can result in slightly longer processing times. We’re monitoring the situation and will keep optimizing as needed.

  4. resolved Jan 23, 2026, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2025 Delayed email delivery 1d 22h

Started Oct 21, 2025, 02:34 PM UTC· resolved Oct 23, 2025, 01:01 PM UTC

  1. identified Oct 21, 2025, 02:34 PM UTC

    We have identified an issue with our outbound emails being rejected and are investigating. This is impacting email alerting and registration confirmation emails.

  2. monitoring Oct 21, 2025, 03:13 PM UTC

    Email sending has been reenabled.

  3. resolved Oct 23, 2025, 01:01 PM UTC

    This issue has been resolved. Please reach out to [email protected] if you continue to have email deliverability issues.

Read the full incident report →

Major August 8, 2025 Delayed document processing 55m

Started Aug 08, 2025, 03:02 AM UTC· resolved Aug 08, 2025, 03:58 AM UTC

  1. investigating Aug 08, 2025, 03:21 AM UTC

    An incident is currently in progress. The cause has been identified and is causing delays in the creation of new documents. Service is expected to be restored within approximately 30 minutes. We apologize for any inconvenience caused.

  2. investigating Aug 08, 2025, 03:34 AM UTC

    The issue has been identified and a fix is in progress. We’re doing everything we can to restore the service as soon as possible.

  3. monitoring Aug 08, 2025, 03:45 AM UTC

    The issue has been identified and a fix is in progress. Service should be back within about 15 minutes.

  4. resolved Aug 08, 2025, 03:58 AM UTC

    The issue is now fixed

Read the full incident report →

Minor July 3, 2025 Delayed document processing 19h 42m

Started Jul 03, 2025, 04:03 PM UTC· resolved Jul 04, 2025, 11:46 AM UTC

  1. investigating Jul 03, 2025, 04:03 PM UTC

    We are currently observing increased delays in processing due to heavy server load. Documents will process once this queue has subsided. If Force OCR is enabled, temporarily disabling this will improve processing times.

  2. monitoring Jul 03, 2025, 08:37 PM UTC

    Queue activity has returned to normal levels and we are monitoring the situation.

  3. resolved Jul 04, 2025, 11:46 AM UTC

    This issue has been resolved in full. We will be improving the infrastructure so events like this do not happen moving forward. If you have any questions, please reach out to us at [email protected].

Read the full incident report →

Minor June 12, 2025 Delayed document processing 9h 29m

Started Jun 12, 2025, 06:51 PM UTC· resolved Jun 13, 2025, 04:21 AM UTC

  1. monitoring Jun 12, 2025, 06:51 PM UTC

    Processing delays have subsided, and all delayed documents have been processed - we are monitoring the servers and will look to have a root cause identified in the next 24 hours.

  2. investigating Jun 12, 2025, 06:51 PM UTC

    Some scanned documents may take longer than usual to be analyzed and processed, we are currently investigating why this is happening.

  3. resolved Jun 13, 2025, 04:21 AM UTC

    Processing is back to normal and all queues are cleared. Incident was due to a global outage at our cloud Provider.

Read the full incident report →

Minor May 19, 2025 Degraded scanned document performance 22h 16m

Started May 19, 2025, 06:57 PM UTC· resolved May 20, 2025, 05:13 PM UTC

  1. identified May 19, 2025, 06:57 PM UTC

    Some scanned documents may take longer than usual to be analyzed and processed. We suggest disabling the "Force OCR" setting if not strictly necessary, to improve performance. An incident case has been opened with our service provider. We'll keep you posted on the progress on this issue.

  2. resolved May 20, 2025, 05:13 PM UTC

    Incident is resolved.

Read the full incident report →

Minor January 22, 2025 Export data columns unexpectedly reordered 1d 4h

Started Jan 22, 2025, 10:16 AM UTC· resolved Jan 23, 2025, 03:04 PM UTC

  1. identified Jan 22, 2025, 10:16 AM UTC

    We identified an issue that could impact your workflow if you integrate with Google Sheets and rely on column order. We are working on a fix to reinstate the former behavior.

  2. identified Jan 22, 2025, 11:23 AM UTC

    We are testing a tentative fix. We will deploy as soon as we are confident that this solves the problem.

  3. monitoring Jan 22, 2025, 02:15 PM UTC

    A fix is now in place. We are monitoring the situation.

  4. resolved Jan 23, 2025, 03:04 PM UTC

    Issue is resolved. Thank you for your patience and understanding.

Read the full incident report →