Incidents reported on status page for Smartr365 https://status.smartr365.com/ https://d1lppblt9t2x15.cloudfront.net/logos/9f4aa5a122d8868242570032b9bec5f2.png https://status.smartr365.com/ en https://status.smartr365.com/incident/852941 Mon, 23 Mar 2026 08:51:00 -0000 https://status.smartr365.com/incident/852941#1749d9f68d3033b0e5674755a8b9aa06a3882baec3a450edc42ce96d09310d09 The issue affecting authentication email delivery and user sign-in is now largely resolved. Over the past several days, we observed significantly reduced email delivery rates, which led to failed sign-in attempts and temporary account lockouts. Since March 20th, delivery and sign-in success rates have returned to normal levels across all major providers. Notably: Apple iCloud email delivery has recovered from ~20% to near 100% Corporate and Microsoft 365 domains have returned to expected levels (92–100%) Overall sign-in success rates are now consistently above 95% We are now seeing only a very small number of isolated cases, compared to the elevated failure rates earlier in the incident. We believe the issue has been mitigated through a combination of Microsoft-side improvements and adjustments made to our sign-in controls. We will continue to monitor closely, but at this stage the incident can be considered largely resolved. Thank you for your patience while we worked through this issue. https://status.smartr365.com/incident/852941 Sat, 21 Mar 2026 08:03:00 -0000 https://status.smartr365.com/incident/852941#ff1dbb906cc15c177651dfc52584476368e964073fe64a434e2ecae86109f3d3 While we continue working with Microsoft on the underlying email delivery issue, we have implemented adjustments to our sign-in security settings to reduce the likelihood of users being temporarily locked out. These changes are designed to provide a smoother sign-in experience while maintaining account security. If you are still experiencing issues accessing your account, please contact your internal IT team for assistance. We will continue to provide updates as we work toward a full resolution. https://status.smartr365.com/incident/852941 Thu, 19 Mar 2026 16:30:00 -0000 https://status.smartr365.com/incident/852941#b83ce96ac89688321f808b0646e758b9376c67e55d104cb20126a9296d9a086e We’ve identified that, for some customers using Microsoft services, authentication emails (including sign-in and password reset emails) may be held in Microsoft’s security systems. If you are not receiving these emails, we recommend contacting your internal IT team, who can review and release any held messages. For customers who manage their own IT, you may be able to check your organisation’s quarantine via the Microsoft Security portal: https://security.microsoft.com/quarantine We are continuing to work with Microsoft to resolve the underlying delivery issue and prevent further disruption. Thank you for your continued patience while we work toward a full resolution. https://status.smartr365.com/incident/852941 Thu, 19 Mar 2026 14:01:00 -0000 https://status.smartr365.com/incident/852941#508c27310e64b669a6959c4e4f9ed657e561d060744a5b0b9e5cf15e42166622 We are currently investigating an incident affecting user sign-in. Since March 17th, some users have been unable to receive sign-in or password reset emails, which has prevented successful authentication. Repeated sign-in attempts have, in some cases, triggered automated security protections, resulting in temporary account lockouts. We are actively working with Microsoft to resolve the issue, restore email delivery, and ensure affected users can safely regain access to their accounts. We understand how disruptive this is and appreciate your patience while we work toward a resolution. Further updates will be provided as soon as more information becomes available. https://status.smartr365.com/incident/850486 Mon, 16 Mar 2026 12:40:00 -0000 https://status.smartr365.com/incident/850486#d8362656c9d31a62afb27147e18d9bc118c7469dcc95795ad572c3fa17836feb A fix has now been deployed and document functionality within the Network Case Review Portal has been fully restored. The issue was caused by a change introduced during the scheduled overnight release (v1.14.64) which affected document loading and processing. We apologise for any inconvenience caused and will continue to monitor the service. https://status.smartr365.com/incident/850486 Mon, 16 Mar 2026 09:15:00 -0000 https://status.smartr365.com/incident/850486#db575e8edc2c035f4f761b9eeb311e6795f1d5f9c3ef117464ada6608c620987 Our development team identified that a change introduced in the latest release was affecting the loading and processing of documents within the Network Case Review Portal. Work began immediately to implement and test a fix to restore normal service. https://status.smartr365.com/incident/850486 Mon, 16 Mar 2026 06:45:00 -0000 https://status.smartr365.com/incident/850486#d8ce4dacea8f15294c950a0238b2816cca4529db90c5c0b6132f942fd0fba452 Smartr became aware of an issue affecting the document functionality within the Network Case Review Portal. The issue began following a scheduled overnight release (v1.14.64). Our technical team began investigating the cause and working on a resolution. https://status.smartr365.com/incident/850292 Fri, 13 Mar 2026 11:00:00 -0000 https://status.smartr365.com/incident/850292#50b038876ff305c9cf9b2e49f42d6ae5fb9d9f8d75debd61f943f41fb93da37f The issue affecting access for some brokerages has now been resolved. The disruption was caused by an expired security certificate impacting a subset of customers, primarily those onboarded more recently. A renewed certificate has now been deployed and fully propagated across the platform, and service has been restored. We apologise for the disruption and will continue to monitor the platform. https://status.smartr365.com/incident/850292 Fri, 13 Mar 2026 09:00:00 -0000 https://status.smartr365.com/incident/850292#f238f31219a0cb173494073239653207ebd9e0960d2e4d80982c5594b253ed7d Smartr became aware of an issue affecting access for a small number of brokerages this morning following a high volume of support reports. Our technical teams began investigating immediately and initiated internal incident response procedures to identify the cause and restore service as quickly as possible.