signNow Outage History
10 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded signNow Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 17, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Sep 4, 2026 | University SignNow UnavailableIssue is resolved | 8 min | Resolved |
| Jul 5, 2026 | Scheduled Maintenance Announcement: US environmentThe scheduled maintenance has been completed. | 15 min | Scheduled |
| May 27, 2026 | Error when sending a documentThis incident has been resolved. | 1h 27m | Resolved |
| May 6, 2026 | Team documents are not displaying properlyThis incident has been resolved. | 3h 14m | Resolved |
| Mar 11, 2026 | Issue with sending SMS invitesThe reported issue has been successfully resolved. All systems are functioning normally. | 5h 8m | Resolved |
| Mar 1, 2026 | Microsoft Email Filtering Impact on SignNow Invite Delivery## **Summary** Between **February 23 and February 28, 2026**, changes in Microsoft’s email filtering behavior intermittently affected delivery of some SignNow invite emails sent to Microsoft-hosted email services… | 0 min | Resolved |
| Feb 10, 2026 | Website is not loading properlyThis incident has been resolved | 10h 3m | Resolved |
| Jan 22, 2026 | Email Delivery DelaysThis incident has been resolved. | 13 min | Resolved |
| Jan 8, 2026 | Issue with Support Email DeliveryThe issue has now been resolved, and email support is fully operational again. | 10h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next signNow incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This signNow Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before signNow acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single signNow outage in this window ran 10h 28m, against a mean recovery of 3h 7m. If you depend on signNow in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.