Scrive Outage History

Scrive had 36 outages in the last 2 years totaling 1230h 7m of downtime — averaging 1.5 incidents per month.

There were 36 Scrive outages since June 4, 2025 totaling 1230h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.scrive.com

Major October 15, 2025

Issues with Branded domain on eSign Online

Detected by Pingoru: Oct 15, 2025, 07:02 AM UTC
Resolved: Oct 15, 2025, 07:17 AM UTC
Duration: 14m

Affected: eSign Online

Timeline · 2 updates

investigating Oct 15, 2025, 07:02 AM UTC

We’re currently experiencing degraded performance with the login with branded domains on our eSign service. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. In the meantime users can login directly to scrive.com Updates will follow in a timely manner.
resolved Oct 15, 2025, 07:17 AM UTC

This incident has been resolved.

Read the full incident report →

Minor October 1, 2025

Authentication Issues Affecting Certain Integrations

Detected by Pingoru: Oct 01, 2025, 06:00 AM UTC
Resolved: Oct 08, 2025, 09:22 AM UTC
Duration: 7d 3h

Affected: Google Docs AddonLimeNetDocumentsOffice Add-In

Timeline · 3 updates

investigating Oct 01, 2025, 01:38 PM UTC

Some users may currently experience authentication issues when logging in to Scrive via Single Sign-On (SSO) through certain integrations, such as Scrive for SuperOffice or Microsoft Office. We have identified the cause and are working on a resolution. We will provide further updates as more information becomes available and will notify you once the issue has been fully resolved.
investigating Oct 02, 2025, 02:45 PM UTC

We are continuing to investigate this issue.
resolved Oct 08, 2025, 09:22 AM UTC

This incident has been resolved.

Read the full incident report →

Minor September 30, 2025

Help Center - Partial Outage

Detected by Pingoru: Sep 30, 2025, 12:46 PM UTC
Resolved: Sep 30, 2025, 03:46 PM UTC
Duration: 2h 59m

Affected: Help Center

Timeline · 3 updates

identified Sep 30, 2025, 12:46 PM UTC

We are currently experiencing an issue affecting our Help Center. This may result in slow loading times, limited access to articles, or certain features not working as expected. Our service provider is actively working to restore normal functionality as soon as possible. We’re sorry for any inconvenience this may cause. We’ll provide updates as soon as we have more information. If you need assistance, please reach out to us via [email protected].
monitoring Sep 30, 2025, 12:49 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Sep 30, 2025, 03:46 PM UTC

This incident has been resolved.

Read the full incident report →

Minor September 26, 2025

Issues with Scrive Extended Compliance

Detected by Pingoru: Sep 26, 2025, 02:18 PM UTC
Resolved: Sep 26, 2025, 02:38 PM UTC
Duration: 19m

Affected: eSign OnlineeSign APIFlow APIeID Hub APIeSign GOID-checkKSI (Guardtime)PAdESRetail eSign AppForms BuilderOffboardingScrive QES

Timeline · 3 updates

investigating Sep 26, 2025, 02:18 PM UTC

We’re currently experiencing degraded performance with Scrive Extended Compliance services due to networking problems on our cloud providers end. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. Users trying to send out documents may be affected. Updates will follow in a timely manner.
investigating Sep 26, 2025, 02:34 PM UTC

We are continuing to investigate this issue.
resolved Sep 26, 2025, 02:38 PM UTC

This incident has been resolved.

Read the full incident report →

Minor September 24, 2025

eSign Online, Go, Flow, API - Degraded performance

Detected by Pingoru: Sep 24, 2025, 12:59 PM UTC
Resolved: Sep 24, 2025, 04:39 PM UTC
Duration: 3h 39m

Affected: eSign OnlineeSign APIeSign FlowFlow APIeSign GO

Timeline · 3 updates

investigating Sep 24, 2025, 12:59 PM UTC

We’re currently experiencing degraded performance with several of our services. Our team is currently working to restore normal performance levels. We apologise for any inconvenience. Updates will follow in a timely manner.
monitoring Sep 24, 2025, 01:22 PM UTC

A fix has been implemented and we are monitoring the results. Updates will follow.
resolved Sep 24, 2025, 04:39 PM UTC

This incident has been resolved.

Read the full incident report →

Minor September 10, 2025

HelpCenter - Degraded performance

Detected by Pingoru: Sep 10, 2025, 02:47 PM UTC
Resolved: Sep 11, 2025, 07:33 AM UTC
Duration: 16h 46m

Affected: Help Center

Timeline · 2 updates

investigating Sep 10, 2025, 02:47 PM UTC

We’re currently experiencing degraded performance with our HelpCenter. Our service providers team is currently working to restore normal performance levels. We apologise for any inconvenience. All users may be affected. Pictures are not shown properly within the guides published. Updates will follow in a timely manner.
resolved Sep 11, 2025, 07:33 AM UTC

This incident has been resolved.

Read the full incident report →

Minor September 10, 2025

Issues with Scrive QES

Detected by Pingoru: Sep 10, 2025, 02:05 PM UTC
Resolved: Sep 10, 2025, 02:56 PM UTC
Duration: 51m

Affected: Scrive QES

Timeline · 2 updates

investigating Sep 10, 2025, 02:05 PM UTC

We’re currently experiencing degraded performance with Scrive QES. Our team is currently working to restore normal performance levels. Users trying to send out documents may be affected. We apologize for any inconvenience.
resolved Sep 10, 2025, 02:56 PM UTC

This incident has been resolved.

Read the full incident report →

Notice September 1, 2025

Email delivery - degraded performance

Detected by Pingoru: Sep 01, 2025, 04:31 PM UTC
Resolved: Sep 01, 2025, 05:34 PM UTC
Duration: 1h 2m

Affected: Email delivery

Timeline · 2 updates

identified Sep 01, 2025, 04:31 PM UTC

We’re currently experiencing degraded performance with our email service. Our service provider is currently working to restore normal performance levels. We apologise for any inconvenience. Updates will follow in a timely manner.
resolved Sep 01, 2025, 05:34 PM UTC

This incident has been resolved.

Read the full incident report →

Minor August 22, 2025

Third-party eID Issue: Swedish BankID

Detected by Pingoru: Aug 22, 2025, 02:50 PM UTC
Resolved: Aug 22, 2025, 03:19 PM UTC
Duration: 29m

Affected: Swedish BankID

Timeline · 2 updates

investigating Aug 22, 2025, 02:50 PM UTC

External eID Swedish BankID is experiencing degraded performance. We are monitoring the situation and will provide and update as it's resolved.
resolved Aug 22, 2025, 03:19 PM UTC

This incident has been resolved.

Read the full incident report →

Minor July 24, 2025

eSign for Microsoft Dynamics - Partial Outage

Detected by Pingoru: Jul 24, 2025, 10:00 PM UTC
Resolved: Jul 30, 2025, 01:04 PM UTC
Duration: 5d 15h

Affected: Dynamics

Timeline · 3 updates

identified Jul 29, 2025, 12:16 PM UTC

We’re currently experiencing a partial outage with Scrive eSign for Microsoft Dynamics. Our team is currently working to restore normal performance levels. We apologize for any inconvenience.
monitoring Jul 30, 2025, 08:38 AM UTC

A fix has been implemented and we are monitoring the results.
resolved Jul 30, 2025, 01:04 PM UTC

We have now identified the cause of the issue and applied a fix. We see no further issues - If you're still experiencing problems, please reach out to our support: [email protected]

Read the full incident report →

Major June 4, 2025

Scrive eSign Office Add-in – Partial Outage

Detected by Pingoru: Jun 04, 2025, 06:00 AM UTC
Resolved: Jul 11, 2025, 03:17 PM UTC
Duration: 37d 9h

Affected: Office Add-In

Timeline · 2 updates

identified Jun 04, 2025, 01:17 PM UTC

We’re aware of issues with the Scrive Office Add-in not working properly in some cases. We’re investigating the issue and working on a fix. If you’re experiencing issues, please ask your 365 admin to uninstall the add-in and reinstall it from AppSource, making sure version 1.1.0.0 is installed. Updates will follow once the issue is fully resolved.
resolved Jul 11, 2025, 03:17 PM UTC

This incident has been resolved.

Read the full incident report →