Is Docparser Down Right Now? Check if there is a current outage ongoing.

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.

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.

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

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.

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

This incident has been resolved.

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

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.

This incident has been resolved.

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.

The api issue has been resolved and the "Normalize Postal Address" filter is working again.

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

This incident has been resolved.

We are continuing to investigate this issue.

Our team is investigating the issue and working on a resolution.

This incident has been resolved, and the OCR services are now available. Affected parsers: Only parsers using Tesseract as an OCR to process documents in languages other than English. We thank you for your patience and support while we worked on a resolution, and we sincerely apologize for any inconvenience it may have caused.

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

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

We regret to inform you that we are having an issue with OCR using Tesseract. We are actively working on resolving the issue. We will provide you with continued updates here. This issue appears to be affecting OCR in languages other than English at this time.

Our Developers have resolved the problem, and our API is working again. We understand how frustrating this situation has been, and we sincerely apologize for the inconvenience it has caused.

Our Developers are actively working on resolving the API issue, but there is currently no estimated time for resolution. We apologize for the inconvenience and appreciate your patience. We will provide you with continued updates here.

We regret to inform you that we are having an issue with API. We are actively working on resolving the issue. We will provide you with continued updates here.

The Docparser application experienced unexpected downtime of 4 minutes from 01:24 AM to 01:28 AM UTC on September 6, 2024, during an infrastructure upgrade. This was an unplanned incident, and we regret any inconvenience it may have caused. Affected services: Our servers did not receive documents and emails uploaded during the incident. Customers can upload them again. All documents in progress were retried after the incident. We assure you our team is committed to preventing such incidents in the future and ensuring the stability of our service. Thank you for your understanding.

This incident has been resolved.

We are having a server outage that is causing issues with uploading. We are investigating this issue.

This incident has been resolved.

We've noticed that some customers are encountering delays in reparsing today. These delays are specifically affecting customers with large-scale reparsing needs, typically involving thousands of files at once. Rest assured, our team is actively addressing the issue and working towards a swift resolution. We apologize for any inconvenience this may cause and appreciate your patience as we work to ensure smooth operations for all our users.

The issue has been resolved. MFA has been re-activated.

We are continuing to investigate this issue.

We are currently investigating working on resolving an issue with our MFA provider. If you use MFA to log in to Docparser, kindly contact support, who can assist you. Meanwhile, out team is working on resolving the issue with no compromise on security of your accounts.

We regret to inform you that there was a disruption in our ability to receive documents via email. The incident occurred from 12:34:03 (UTC) to 12:55:27 (UTC). Emails sent during this period were not received by our servers due to an internal server issue. Regrettably, the error logs did not capture the emails rejected by the server. Our engineering team worked diligently to rectify the issue and recover any affected emails. However, we have personally contacted all affected users and kindly request you to resend any emails sent during the mentioned duration. We apologize for any inconvenience this may have caused and appreciate your understanding.

This incident has been resolved.

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

Slow uploads due to high traffic on the application

Some users were unable to use their existing Google Sheets integrations.

Degraded services due to unexpected database issues resulting from a recent deployment.

This incident has been resolved.

We are investigating an issue with documents taking a longer than usual time to process through the import queue. This page will be updated with any changes.

Users experienced delays in parsing for a period of 60 minutes due to high load.

Users experienced delays in parsing for a period of 10 minutes due to high load.

The main site was unreachable for a period of 10 minutes due to high load.

This incident has been resolved.

We just recovered from a brief database outage which may cause some parsing speed degradation. Speed should be back to normal once the system catches up from the outage. We are also working to kick in upscaling which should help also.

We are continuing to monitor for any further issues.

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

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

We are currently investigating issues with our database systems.

The issue has been fully resolved and this incident will be updated with a postmortem in the next few days.

Processing and importing times have resided at normal levels and we are monitoring the results.

The issue has been identified and our engineers are working towards a solution.

We are investigating an issue with documents taking a longer than usual time to process through the import queue. All documents in queues will be automatically processed when the queues have died down, though this is not happening as quickly as we would like. We are still investigating and will update this page with any changes.

Around 11:05CET we had an increase in server load which caused processing times to be delayed for longer than usual as well as "Bad Gateway" error. The Bad Gateway issue was resolved at ~12:00CET and we are still working on resolving the processing delays issue.

Servers are up and running again after finishing maintenance tasks. If you are using one of our outbound integrations, your webhooks failed during these periods. You will need to retry these failed webhooks in order for us to send your data out afterward.

We will be performing maintenance on our servers on Saturday, September 3, 2022 - 10AM EDT (2 Hours) If you are using one of our outbound integrations, your webhooks will fail during these periods. You will need to retry these failed webhooks in order for us to send your data out afterward.

This incident has been resolved, but we are still investigating the original cause and will update this incident when this investigation has concluded.

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

We are investigating this issue urgently and will update here as soon as more information is available.

The issue has been fully resolved and this incident will be updated with a postmortem in the next few days.

A fix has been implemented, processing times have resided to normal levels and we are monitoring the results.

While we were able to resolve the initial conflict causing the slowdown to all queues, we are currently at all hands investigating a new problem with the data parsing queue moving slower than usual for all new and old documents. We will post further updates as soon as they become available.

The issue has been identified and our engineers are working towards a solution.

We are investigating an issue with documents taking a longer than usual time to process through import, data parsing and integration queues, starting around 0900EDT this morning. All documents in queues will be automatically processed when the queues have died down, though this is not happening as quickly as we would like, even with updates to our server counts. We are still investigating and will update this page with any changes.

From 2300EDT 09/16 to 0500EDT 09/17, there was an issue with our database updating after a server upgrade that caused documents to get stuck and/or not be received by our system. We've resolved the issue and are taking steps to make sure this doesn't happen in the future.

This incident has been resolved and normal service has been restored.

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

Around 1200UTC, we identified that customer parsed data is being held in the integrations queue. The problem has been identified and a fix is currently being implemented.

Around 0430EST we had an increase in server load which caused processing times to be delayed for longer than usual. This issue was fully resolved at ~0700EST with no lost customer data.

This incident has been resolved - our Google Drive integration has full functionality. Please reach out with any issues with Google Drive import to support@docparser.com

A fix has been implemented for our Google Drive integration and we are monitoring results. Please reach out with any issues with Google Drive import to support@docparser.com

We are currently investigating an issue with our Dropbox, Box, and Google Drive cloud upload integrations wherein not all files are being imported when checking a folder. We are still collecting more information on this issue and will follow up with an update as soon as one is available.

We have taken measures to make sure this problem does not happen again: Server monitoring has been bolstered to account for this issue so action is taken before an outage Server configuration has been updated so servers refresh when a new release is merged live If you have any questions or continue to have trouble accessing the app please reach out to support@docparser.com

We have restarted our servers which has restored full functionality to the app - we are still investigating root causes and preventative measures. Customers can now interact with our API, upload files and download parsed data without issue. If you are still receiving 503 errors or having trouble with the app please reach out to support@docparser.com

We are urgently investigating why file uploads, file downloads, and our API interface are unexpectedly returning errors and will have an update shortly.

After releasing our free subscription model, an unexpected error in our code caused documents to not be imported properly. Documents that were uploaded between 0910-1015 EST on April 17th may have been stuck in a parser's Imports Queue - these documents will need to be re-uploaded. Once re-uploaded you can manually delete any remaining documents in your Import Queue.

Around 0300PST, Amazon Web Services reported an issue with increased error rates in a queue that we use (Amazon Simple Queue Service - N. Virginia) which caused documents to be stuck in processing. AWS reported the problem resolved around 3 hours. After this time our team manually pushed through any emails still stuck, and have made repairs to the system so for future outages, documents will automatically be processed after resolution. You can follow Docparser's status here and on the AWS dashboard, as well as the RSS for the queue we use: https://status.aws.amazon.com/ https://status.aws.amazon.com/rss/sqs-us-east-1.rss

Due to a server load related issue, customer webhooks began to queue around 2100EST 01/14. The cause was discovered and remedied so that the same incident won't happen again. The queue was fully resolved at around 1200EST 01/15. Customer alerting on this incident was poor and we pledge to be more vigilant in reporting issues to keep our customers informed. Apologies for the trouble!

This incident has been resolved as of 0750EST, users may now activate their Dropbox and Google Drive cloud upload integrations.

We are currently investigating an issue with our Dropbox, Box and Google Drive API upload integrations. We are aware of some documents being uploaded multiple times causing duplicates, and will issue credits to offset these extra documents uploaded on request.

This incident has been resolved.

We identified the root cause of the problem and fixed it in the meantime. We are back to normal processing speed by now. To prevent this issue from happening again we will scale up our database servers.

We are currently investigating this issue.

Our system show normal processing speed by now.

We were able to correct the issue and deployed a new version of Docparser. The queued-up documents are currently getting processed and we should be back to normal speed in about 30 minutes.

We identified the issue. Our preprocessing queue got stuck because a malformed input file. We are working on preventing this issue from happening again.

We are currently seeing an increase in the preprocessing queue for documents. We are investigating.

This incident has been resolved.

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

We are currently seeing slowed down processing due to a high influx of documents. We are working on scaling up our system.

This issue has been resolved and we are back on normal import speed. Please excuse the trouble caused.

We are monitoring the situation.

We identified and resolved the issue. One of our worker nodes was not importing any files into the Docparser system.

We are currently seeing delayed import times for certain documents.

This incident has been resolved.

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

We are currently investigating this issue.

We successfully upgraded our infrastructure and processing speed should be back to normal.

We are seeing an unusual high traffic peak today and working currently on resolving the issue by scaling up our architecture.

The issue is resolved! Please excuse any inconvenience caused by this.

The root cause for the OCR issue is getting solved right now and a new version will be deployed asap.

We deployed a temporary fix to the problem and are currently monitoring the system.

We identified the source of the issue. It appears that the OCR engine we are using is randomly losing documents. We are working on fixing this issue right now.

We are seeing documents which show up as blank pages after preprocessing for OCR. It seems that this error occurs randomly as some documents are getting processed correctly when uploading them again to Docparser.

We fixed a bug which caused a degraded performance of the Excel download options. In some rare cases, customers were not able to select specific parsing rules in the Excel file download configuration panel.

A bug in our system lead to degraded performance of the Excel download feature. Some parsing rules were not showing up in the Excel file download configuration panel.

We were monitoring the system for one hour and everything seems to work as expected.

A fix was deployed and we are currently monitoring if everything is working again as expected.

We identified the root cause for this issue. This issue affects all parsers which are using a "Merge Fields' parsing rule. A fix will be deployed in the coming minutes.

We received notifications from a couple of customers that documents randomly get stuck in the parsing queue. It seems like the documents are getting parsed (data is extracted), but the status is not updated accordingly.

We identified and fixed the issue. All services are fully operational again.

We are currently seeing incorrect data returned by our postal address parser. It seems that dummy data is returned instead of the real addresses.

Our custom webhooks allow the usage of replacement patterns inside the webhook target URL. This feature was temporarily not working. The issue has been resolved shortly after it was reported.