Looking for an update now? Check the current status, or follow signNow for future changes.
97.3%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
96.7%
30
1
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We are currently investigating an issue affecting access to the SignNow University website. The issue is related to an underlying problem with our Help Center service, which is also impacting the University site.
Our team is actively working to identify the root cause and restore full access as soon as possible. We apologize for the inconvenience and appreciate your patience while we work on resolving this issue.
Legacy Incident Archive
2 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Error when sending a document
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Some users are getting an error message, "There's a problem sending the invite," when sending a document.
Team documents are not displaying properly
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We’ve identified an issue where team documents are not displaying properly for some users. Our team is currently investigating the root cause and working toward a resolution.
