Mesh Security had 16 outages in the last 2 years totaling 51h 29m of downtime — averaging 0.7 incidents per month.
There were 16 Mesh Security outages since July 15, 2025 totaling 51h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are aware of some inbound emails delivery delays on our US infrastructure. Our team is investigating.
Email queues have cleared and latency has returned to normal. Thank you for your patience.
We have identified email delays on our outbound EU infrastructure. Inbound delivery is not impacted. We will provide a status update as soon as possible.
Queues have cleared and latency has returned to normal. Thank you for your patience.
We have identified minor email delays on our US infrastructure. We will provide a status update as soon as possible.
Email processing times have returned to normal and queues have cleared. Thank you for your patience.
We are currently investigating short email delays. We will post an update as soon as possible.
Queue times have returned to normal. Thank you for your patience.
We are currently investigating an issue impacting our detection engine which is resulting in some emails incorrectly receiving a phishing verdict.
A fix has been implemented and we are monitoring.
The issue has been fixed as of 3pm Eastern Time. Unfortunately, we do not have a mechanism to automatically release those emails that were incorrectly given a phishing verdict. Thank you for your patience while we worked through this.
We are currently investigating some inbound delivery queues on our US infrastructure. We will provide an update as soon as possible.
Queue volume is dropping steadily and the infrastructure team is monitoring performance.
Inbound queues have cleared and delivery times have returned to normal. Thank you for your patience.
We are currently investigating this issue.
We have identified the issue and a fix has been implemented.
A fix has been implemented and we are monitoring the results.
Queue times have returned to normal. We're continuing to monitor.
We are currently investigating some inbound delivery queues on our EU infrastructure.
The team has identified the root cause and is working on a fix.
Message processing has returned to normal and all queues have cleared. We will continue to monitor.
The team has identified an issue causing some inbound email delivery delays. A fix is being deployed shortly.
The issue has been resolved and email delivery has returned to normal.
Our infrastructure team has identified some email processing delays on our US service.
Queues have returned to normal and we are monitoring system stability.
We are marking this incident as resolved but will continue to monitor closely.
We are currently investigating an issue where emails are slow to process on Mesh 365 on our US service. Mesh Gateway and Mesh Unified is not impacted.
The issue has been addressed and mails are processing as normal on Mesh 365. We will continue to monitor. Thank you for your patience while we worked on this.
Spoke too soon. Apologies for the miscommunication. Outbound processing queues have returned to normal. There is still a heavy queue Inbound on the US infrastructure with delivery into 365 static. Microsoft are reporting that all services are operational we will continue to monitor ...
We expect all messages to be delivered in ~30 mins. New emails are being delivered as normal.
Mail delivery is functioning as expected. We're continuing to monitor the situation. We're closing out this status.
We're observing slow mail processing on the US infrastructure.
Mail processing queues have returned to normal. We're continuing to monitor our infrastructure. For now everything is operational. There is a maintenance window in Azure this evening which we believe will resolve the the underlying throughput issue within their Networks.
We're observing a recurrence of the issue on Azure whereby emails are slow to process on the US infrastructure. We're currently monitoring the situation and have reached out to Microsoft for a status update.
Mail processing queues have returned to normal. We're continuing to monitor our infrastructure. For now everything is operational.
Microsoft is currently experiencing issues delivering emails to tenants within the EU. This is NOT a Mesh issue and this status is informational. Impacted emails will be temporarily deferred and we will continue to retry delivery. Microsoft Status: "We're investigating an issue in Europe where some users may experience delays when sending and receiving email messages. For more details, please look for EX1144276 in the admin center."
Our infrastructure team has been monitoring the situation. Inbound/outbound emails are being delivered more reliably and email queues are reducing in size. Latest update from Microsoft (EX1144276): "The new throttling rule has successfully been deployed. We’ve received confirmation from some of the previously affected users that they can now send and receive email. Additionally, our telemetry shows that the new throttling rule is having the desired effect and providing relief."
Email traffic has returned to normal and Microsoft has marked the incident as resolved. Microsoft Status: "After monitoring the service and receiving confirmation from previously affected users, we’ve confirmed that impact has been remediated. The service will now resume periodic attempts to deliver emails that were sent during the impacted period."
We are aware that one of our outbound IP addresses was listed on Spamhaus' RBL. This IP has been removed from our sending relays and the team is actively working with Spamhaus to identify a root cause. At this time, we do not anticipate any ongoing impact to email delivery and we are closely monitoring for further reports. No action is required from end customers or partners.
Our team has received further feedback from Spamhaus earlier this morning. The listings were caused by an end user emailing a spamtrap/honeypot operated by Spamhaus. The honeypot domain is a typosquat of a well known brand and the emails sent were not malicious traffic. We have reached out to the MSP so they can advise their end user of the mistake/typo.