We are currently experiencing slowness in the eSign service. For users this results in slower loading. We are currently investigating the cause.
After all parties have signed a document, the final sealing is slow. For the person who signs a document, the result is a loading page after he/she has signed.
We are working on getting the sealing back to normal as soon as possible.
We are currently having issues with the document sealing after all parties have signed a document. Our engineers are investigating and we will update as soon as we know more.
The document queue is now empty and sealing is back to normal speed.
We have now fixed the root cause for the issue. Sealing is working again, however due to some backlog of documents that needs to be sealed, you might experiencing slowness for the next half hour while the queue is being emptied.
We have identified what causes sealing to be slow (which makes the signing page, after a customer has signed a document, not to load). We are currently working on finding a fix.
We are currently experiencing slow operation in the Core eSigning service. You may intermittently experience slower loading times and response times in connected services. We are currently investigating.
We are having intermittent issues with access to Scrive Online. Our engineers are investigating with highest priority.
After an update, last name needs to be added for the sender of a document. We are urgently working on a fix for this.
If you are having trouble right now to send a document or with an ongoing process, go to Account > User and add a last name.
We are currently experiencing slow delivery of emails from our service. If you have an urgent document that is not delivered, we recommend that you use an alternative delivery method such as SMS or link. For instructions on how to use the method "link", please see the following article: https://support.scrive.com/hc/en-us/articles/4403047184274-How-to-use-invitation-method-Link-instead-of-E-mail-
Our email provider reported that the issue has now been solved and deliveries should be back to normal.
The third party solution that we use for email sending is experiencing email delivery delays for the EU region and they are currently investigating (https://status.mailgun.com/).
In case you need to deliver a document for signing urgently, see previous update for information on alternative ways of delivery in Scrive.
Customers who use the API to create processes with phone numbers that are not valid international numbers (i.e. starting with a "+" and a country code) cannot finish their signing processes. We are implementing a change to address this. We estimate that it will be live within two hours.
We are currently experiencing slow operation of the core service. We are investigating the cause of this. Updates will follow once more information is available.
We have now rolled out a fix for the underlying issue which will prevent it from recurring. We can also see that the service is back to normal.
We are experiencing occasional degradation of some core Scrive services. We have found the cause and a hot-fix is being prepared. It will be rolled out with the next few hours pending quality assurance and testing. We will let everyone know when it happens.
We are once again experiencing slow loading times in the core eSign service. You may experience difficulties logging in and using Scrive intermittently. We are investigating the cause of the issue.
The service is back to normal operational again. We are monitoring the situation.
Our third party email-provider reported that they are currently experiencing delays with the delivery of emails. We are monitoring the situation and will update the status accordingly.
If you have an urgent document that is not delivered, we recommend that you use an alternative delivery method such as SMS or link. For instructions on how to use the method "link", please see the following article: https://support.scrive.com/hc/en-us/articles/4403047184274-How-to-use-invitation-method-Link-instead-of-E-mail-