Historical record of incidents for SignRequest
Report: "Processing delays"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
Report: "Performance Issues"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Performance Issues"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Delayed document processing"
Last updateThis incident has been resolved.
We are currently investigating this issue.
Report: "Conversion Issues"
Last updateThis incident has been resolved.
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 this issue.
Report: "Document Conversion Issues"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating intermittent issues with the document conversion process!
Report: "SignRequest unavailable"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue and will provide additional information as it becomes available.
We are continuing to work on a fix for this issue and will provide additional information as it becomes available.
We are continuing to work on a fix for this issue.
The issue has been identified and we're working on a fix!
Report: "SignRequest reminders not delivered"
Last updateDue to an email delivery system incident some SignRequest reminder emails have not been delivered in the last week. This does not apply to scheduled emails in the future, they will be emailed correctly in the future from now on. If you depend on this reminder, you can still manually trigger one from your account. We're sorry for the inconvenience this might have caused.
Report: "Delayed document processing"
Last updateThis incident has been resolved.
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 this issue.
Report: "Long waiting times when a new document is uploaded on signrequest.com"
Last updateThis incident has been resolved
We have tracked down another potential issue to the performance of the application. We mitigated that issue and we are now monitoring the results.
We are having performance issues: converting documents and other similar actions take a longer time than usual at peak times. We increased server capacity and we are monitoring the situation to see the effects on processing times.
We are currently investigating this issue
Report: "Long waiting times when a new document is uploaded on signrequest.com"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
Emergency maintenance done, monitoring.
Emergency maintenance in progress
We have identified an issue for which we need to do emergency maintenance.
We are continuing to investigate this issue.
We are currently investigating an issue related to long waiting times when a new document is uploaded on signrequest.com
Report: "SignRequest affected by AWS downtime"
Last updateThis incident has been resolved.
AWS connectivity is coming back
We are currently investigating this issue.
Report: "Service intermittently unavailable"
Last updateWe deployed a fix and we are monitoring the results.
We've identified an issue affecting our web application. We're currently working on a fix.
Report: "Service intermittently unavailable"
Last updateThis incident was resolved and the applications are available.
A fix has been implemented and we are monitoring the results.
We are currently investigating the systems to understand why some of the requests are failing.
Report: "Service unavailable"
Last updateWe alleviated the impact and all systems are now available.
We are under a DDOS attack. We are working to restore the service.
Report: "Service unavailable"
Last updateThis incident has been resolved
We are currently investigating this issue.
Report: "Service unavailable"
Last updateThe incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and we are currently deploying the system with the fix.
Sending sign requests is not working. Email sending is stopped. We continue to investigate.
We are currently investigating the issue
Report: "signrequest.com unreachable"
Last updateThe application at signrequest.com did not load after a regular release deployment.
Report: "API requests that specify the signer language fail with a validation error"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and we are working on a fix.
Report: "Service unavailable"
Last updateDuring a release deployment the application was unavailable for 5 minutes.
Report: "Email sending impaired"
Last updateThis incident was resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "System impaired"
Last updateThis incident has been resolved.
We are currently investigating this issue.
Report: "System impaired"
Last updateThis incident has been resolved.
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 this issue.
Report: "Single Sign-On (SSO) login with custom identity providers not available"
Last updateThe incident has been resolved and Single Sign-On (SSO) login with a custom identity provider is now working.
A fix has been implemented and we're monitoring the results.
We've identified the issue and we're working on a fix.
We are currently investigating this issue.
Report: "Service unavailable"
Last updateThis incident has been resolved.
We are continuing to investigate this issue.
We are currently investigating 502 errors thrown when accessing signrequest.com We discovered that traffic was directed to stopped servers. We fixed the list of active services in our load balancer and now we're monitoring the effects.
Report: "Service unavailable"
Last updateDuring a maintenance deployment we experienced intermittent service unavailable for 5 minutes.
Report: "Service unavailable"
Last updateThe incident has been resolved.
A fix has been implemented and we are monitoring the results.
Report: "Redirect to 404 after signing a document in the dutch language interface"
Last updateAfter a user signs a document using the dutch language interface, we show this page by default https://signrequest.com/nl/landing/bevestiging-getekend. Between Jan 7th and Jan 14th, the default page: https://signrequest.com/nl/landing/bevestiging-getekend was not accessible. Our default page is not used for team documents where "Landing page" is set as a team setting.
Report: "Partial outage when using the legacy prepare document page."
Last updateWe had a partial outage for users on the legacy system / design that affected document preparation. In the page preparing your document, you were not able to add new contacts. In the page preparing your document, the new added placeholders were not saved in the backend (silently discarded after clicking Sign and Send). The consequences were that the signers of your document could not see a place to sign. The issue persisted since the release on Thursday, 2020-12-10, 11:00 CET until Friday, 2020-12-11, 15:45 CET
Report: "SignRequest service unavailable"
Last updateDuring a maintenance deployment we had downtime for less than a minute. We are investigating the reasons for the downtime.
Report: "Service unavailable"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "SignRequest service unavailable"
Last updateFor about 2 minutes the service was unavailable due to an error in our systems.
Report: "SignRequest service unavailable"
Last updateFor about 10 minutes the service was unavailable due to an error in our systems.
Report: "SalesForce integration"
Last updateThis incident has been resolved.
The issues that prevented users to send documents using the Salesforce integration are now solved.
We are currently investigating an issue with our SalesForce integration, which prevents (some) users from using the SignRequest service.
Report: "SignRequest service unavailable"
Last updateAugust 13 2020 - TLS certificate incident **Summary and key takeaways** * Our certificate expired on August 13, 2020. * Some of our customers experienced service outages for up to 1 hour. * The issue has been fully mitigated, and the service availability was restored for everyone. On August 13, 2020, 12:00 UTC, we experienced a rare situation where our TLS certificate expired. In theory, this isn’t anything unusual. Certificates expire all the time. But on August 13th, the expiring certificate exposed an underlying issue which made our API and website unavailable for some of our customers. On August 13th, a second after 12:00 UTC when our certificate expired, our Engineering team got notified that there was a certificate problem with our service. This was an unexpected message as our certificates are set up to renew automatically. A quick verification in the browser also confirmed that everything seemed abnormal and that the API was not responding correctly. We immediately took action to manually renew our certificate in AWS certificate manager. This is when we realized that our certificate was ineligible for automatic renewal and according to AWS we have received a notification. We checked the logs and our Health Dashboard and found this to be the case. The direction of the investigation quickly changed when we realized this. We investigated the error message in the logs when trying to renew our certificate and we found that our DNS Certification Authority Authorization \(CAA\) record was the culprit and our investigation into why is ongoing. We proceeded to request a new certificate at 12:34 UTC on August 13, 2020, and we were issued a new certificate at 12:38 UTC on August 13, 2020. We immediately updated our systems with the new certificate and our services were operational at 12:40 UTC on August 13, 2020 again. We updated the status page at 12:07 UTC on August 13, 2020 with the information we had, dedicated people to respond to emails coming to our support and started to work on mitigations of what we thought was the source of the problem. We have implemented more robust metrics and error tracking and set up alarms to notify us in advance when certificates are about to expire in order for us to keep providing an uninterrupted service to our customers.
This incident has been resolved.
We are experiencing a service interruption due to a failed automatic certificate renewal.
We are currently investigating.
Report: "Prepare document service interruption"
Last updateBetween 12:00 and 13:30 CET we've faced a service interruption which prevented a small set of users to prepare documents before sending them out to the recipients. After identifying the issue we've rolled back to the previous stable version. We will investigate what caused this issue and if necessary publish an analysis (post-mortem).
Report: "List of signers missing in API response"
Last updateDocuments retrieved from the API were returned without the signer list. We've rolled back the change which caused this behavior and we will investigate what caused this problem.
Report: "Database maintenance"
Last updateThs incident has been resolved. We’re going to write a postmortem about the events the led to this downtime on this status page asap.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
Maintenance of our database takes longer than expected.
Report: "Database Issue"
Last updateThis incident has been resolved.
Database found the root cause of the issue and fixed it. Everything should be operational now!
We are working on a fix and expect to be back up within the next 20 minutes.
We are continuing to investigate this issue.
Our central database went down, all services are currently unavailable.
Report: "Documents could not be loaded for some users"
Last updateBetween 10:30 AM and 6:30 PM PDT, our upstream provider AWS experienced intermittent errors with resolution of some AWS DNS names. Beginning at 5:16 PM, a very small number of specific DNS names experienced a higher error rate. Our documents s3 domain was one of them. These issues have been resolved.
Report: "Downtime due to database issue"
Last updateThis incident has been resolved.
We are continuing to monitor for any further issues.
We've implemented a fix for the database issue and are monitoring for any further issues.
We've identified an issue causing downtime due to an issue with our database. We're working on a solution and will provide an ETA once known.
Report: "helpdesk down due to cloudflare downtime"
Last updateThis incident has been resolved.
For more information see: https://www.cloudflarestatus.com/
Report: "Temporary less performance"
Last updateFor a period of 5 minutes we experienced performance issues with our database. All systems are performing as expected again.
Report: "Document search impaired"
Last updateThis incident has been resolved.
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 this issue.
Report: "API with file_from_url impaired"
Last updateThis incident has been resolved.
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.
Report: "Converting cluster issues"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Cache cluster failure"
Last updateThis incident has been resolved.
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 this issue.
Report: "Webservers down"
Last updateThis incident has been resolved.
We are currently investigating this issue.
Report: "Login impaired"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
Report: "Our upstream payment processor Stripe is having issues"
Last updateThis incident has been resolved.
We are currently investigating this issue.