Docparser Outage History

Docparser is up right now

Pingoru has recorded 51 incidents for Docparser: 3 in the last 12 months and 1 in the last 90 days.

Source: status.docparser.com

51incidents recorded
3last 12 months
1last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Docparser 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 202600 of 720 (0%)
May 202619 of 744 (1%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 564 (0%)

Incidents, newest first

Notice October 21, 2026 Security Update – CVE-2026-109618 and CVE-2026-109619 –

Started Oct 21, 2026, 06:00 PM UTC· resolved Oct 21, 2026, 06:00 PM UTC

  1. resolved Oct 22, 2026, 07:14 PM UTC

    We are aware of the recently disclosed critical PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Our engineering team has completed the necessary security updates to address these vulnerabilities in Docparser as of October 21, 2026. The updated application has been successfully deployed, and no action is required from customers.

Read the full incident report →

Notice May 5, 2026 Elevated 502 Errors 9h 7m Docparser Application

Started May 05, 2026, 01:07 PM UTC· resolved May 05, 2026, 10:14 PM UTC

  1. investigating May 05, 2026, 01:07 PM UTC

    We are currently investigating an issue where some users are experiencing 502 Bad Gateway errors when accessing Docparser. Our team is actively working to identify the root cause and restore full service as quickly as possible. We will provide further updates as soon as more information becomes available.

  2. identified May 05, 2026, 01:07 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 05, 2026, 01:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 05, 2026, 10:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 2, 2025 System Unavailable 44m Docparser Application

Started Dec 02, 2025, 06:02 PM UTC· resolved Dec 02, 2025, 06:46 PM UTC

  1. investigating Dec 02, 2025, 06:02 PM UTC

    We are currently investigating an issue affecting our production servers. The application is temporarily unavailable.

  2. resolved Dec 02, 2025, 06:46 PM UTC

    This incident has been resolved. Note to users: Any documents that were sent into Docparser during the outage would not have processed and will need to be resent for processing.

Read the full incident report →

Minor March 21, 2025 Textract OCR failing 1h 37m Docparser Application

Started Mar 21, 2025, 12:31 PM UTC· resolved Mar 21, 2025, 02:09 PM UTC

  1. investigating Mar 21, 2025, 12:31 PM UTC

    We regret to inform you that we are having an issue with OCR using Textract. We are actively working on resolving the issue. We will provide you with continued updates here. Apologies for the inconvenience caused here.

  2. identified Mar 21, 2025, 12:52 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Mar 21, 2025, 02:02 PM UTC

    A fix has been implemented and new documents are being processed using Textract OCR. Documents that have not been processed prior to the fix will be processed in due course.

  4. resolved Mar 21, 2025, 02:09 PM UTC

    This incident has been resolved and all documents have now been processed. Thank you for your patience and support while we worked on a resolution We sincerely apologize for any inconvenience this incident may have caused.

Read the full incident report →

Notice December 1, 2024 Files API Error –

Started Dec 01, 2024, 03:00 PM UTC· resolved Dec 01, 2024, 03:00 PM UTC

  1. resolved Dec 05, 2024, 09:52 AM UTC

    Some customers experienced issues when uploading multiple documents simultaneously. Due to infrastructure load, the Files API was intermittently returning 504 errors. The issue was promptly detected and resolved within an hour. All affected services are now fully operational. Our engineering team has implemented necessary measures to prevent similar incidents in the future. We sincerely apologize for any inconvenience caused and appreciate your patience and understanding. If you have any questions or concerns, please contact our support team. Thank you, The Docparser team

Read the full incident report →

Minor November 18, 2024 UI Performance Degradation 3d 12h Docparser Application

Started Nov 18, 2024, 05:49 PM UTC· resolved Nov 22, 2024, 06:27 AM UTC

  1. monitoring Nov 18, 2024, 05:49 PM UTC

    Docparser users experienced slower-than-usual performance on the site over the weekend. This has since been resolved, and the site is now operating normally. We apologise for any inconvenience caused during this time and appreciate your patience and understanding. Our team has implemented measures to minimise the likelihood of similar issues in the future. Thank you for your continued support.

  2. monitoring Nov 20, 2024, 04:48 PM UTC

    No major issues have been reported. Minor parsing slowdown with specific document types observed. Fix is in progress.

  3. resolved Nov 22, 2024, 06:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 11, 2024 File import delay 39m Docparser Application, HTTP REST API

Started Nov 11, 2024, 05:28 PM UTC· resolved Nov 11, 2024, 06:08 PM UTC

  1. investigating Nov 11, 2024, 05:28 PM UTC

    We are currently experiencing an issue where files are stuck in the import queue due to a failure in our autoscaling groups for file preprocessing. Our engineering team is actively working to resolve this as soon as possible to ensure files are processed promptly. We apologize for any inconvenience this may be causing and appreciate your patience as we address the issue. We will provide further updates as soon as we have more information. Thank you for your understanding.

  2. resolved Nov 11, 2024, 06:08 PM UTC

    This incident has been resolved.

Read the full incident report →