signNow Outage History

## **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, including Outlook, Hotmail, Live, and Microsoft 365. SignNow systems were operating normally during this period. Email messages were successfully transmitted from SignNow infrastructure and accepted by Microsoft servers. However, Microsoft’s filtering systems intermittently prevented some of these messages from reaching recipient inboxes. Microsoft later confirmed aggressive spam filtering behavior affecting legitimate email traffic from certain senders and applied mitigation while tuning their filtering models. After confirmation from Microsoft that mitigation had been applied, SignNow proactively **re-sent affected unsigned invites** and notified impacted document owners. Email delivery behavior is currently stable and continues to be monitored. ## **Timeline** **February 23, 2026**Early signals of email delivery issues begin to appear related to Microsoft-hosted email domains. **February 26, 2026**SignNow begins receiving customer reports that some invite emails sent to Microsoft domains are not reaching recipient inboxes. **February 27, 2026**Engineering investigation confirms that emails are successfully transmitted from SignNow infrastructure and accepted by Microsoft servers. SignNow escalates the issue to Microsoft and begins collaborating with affected customers to collect delivery traces. **February 28, 2026**Microsoft confirms aggressive spam filtering behavior affecting legitimate emails and applies temporary mitigation. **March 1, 2026**Microsoft confirms mitigation has been applied broadly. **March 2, 2026**SignNow automatically re-sends affected unsigned invites to ensure recipients receive the documents. **March 4, 2026**Targeted communication is sent to document owners whose invites may have been affected. ## **Root Cause** The incident was caused by **Microsoft spam filtering behavior driven by machine-learning detection models** that intermittently classified some legitimate emails as suspicious. Although SignNow messages were successfully transmitted and accepted by Microsoft mail servers, some emails were filtered before reaching recipient inboxes. A sender header configuration detail may have increased sensitivity to Microsoft filtering behavior for certain messages. This configuration has since been reviewed and adjusted. ## **Impact** During the affected timeframe: * Some invite emails sent to Microsoft-hosted domains experienced delivery delays or filtering. * The issue was **intermittent** and did not affect all messages. * A subset of senders who frequently send documents to Microsoft-hosted domains experienced higher likelihood of impact. SignNow received a limited number of customer reports related to missing invite notifications. Each report represented multiple recipients, meaning the number of impacted recipients was higher than the number of reported cases. ## **Mitigation and Actions Taken** During the investigation, SignNow took the following steps: * Investigated email delivery logs and confirmed successful transmission from SignNow infrastructure * Adjusted email header configuration to reduce filtering sensitivity * Escalated the issue to Microsoft support * Collaborated with affected customers to gather delivery traces * Monitored delivery behavior across Microsoft-hosted domains * Automatically re-sent affected unsigned invites * Proactively notified impacted document owners ## **Current Status** Based on Microsoft confirmation and subsequent delivery validation, the issue is considered **resolved**. SignNow continues to monitor delivery performance to ensure consistent email delivery to Microsoft-hosted domains.