SMX Cybersecure Email had 5 outages in the last 2 years totaling 2h 18m of downtime — averaging 0.2 incidents per month.
There were 5 SMX Cybersecure Email outages since June 6, 2025 totaling 2h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 12:00 am and 1:30am Microsoft experienced issues with their Azure network which affected the routing of traffic to some domains hosted on Azure. This would have impacted outbound email flow during this period. This was resolved at just after 1:30am on Sunday morning .
We are currently aware of an issue where the logs in the SMX email admin portal are not displaying at present. Mail flow is not impacted . We are investigating this issue at present and we will update you once we have further information.
This issue has now been resolved , thank you for your patience.
Adjustment to the Quarantine Self-Release notification emails: You may notice that the SMX logo has been removed from the top of the quarantine self release emails . We found that the logo was not rendering correctly for users on Microsoft Outlook, causing display issues. To ensure the email remains clean, readable, and consistent across all platforms and devices, we have decided to remove the SMX logo from the top of all QSR emails. All links and functionality within the email remain exactly the same.
We are currently seeing an increase in false positive issues due to a misclassification of emails with one of our scanning engines, we are currently working to resolve this issue as soon as possible. For any urgent emails you can add a temporary whitelist in the SMX email admin portal. Further updates to this issue will given as soon as they are known.
This issue has now been resolved and any rejected emails can be sent again now. We apologise for any inconvenience caused .
At present there is an issue where users are not able to log into the SMX email admin portal. We are currently working on this issue to resolve this as soon as possible. Further updates regarding this will posted to this status page once they are known.
This incident is now resolved.