Is CodeTwo down?

We're observing delays in email delivery in the Germany West Central region. We're investigating this right now. It looks like degraded performance of Exchange Online Protection (EOP). Signatures are added normally.

We’ve confirmed that the delays are due to degraded availability of Exchange Online Protection in the Germany West Central region and are not related to CodeTwo. We’ve contacted Microsoft and we’re actively monitoring the situation.

We’re continuing to monitor the situation. Email signatures are being appended correctly. However, delivery of messages with signatures is still delayed due to an issue with Microsoft Exchange Online Protection servers, which are experiencing degraded performance and are processing messages from our service slower than usual. We can see that the issue is widespread in Germany. Other services that rely on the Exchange Online mail flow pipeline are experiencing similar delays in this region. Microsoft is currently working to resolve the problem, and we are actively monitoring their progress. Thank you for your patience. We’ll provide another update in 90 minutes or sooner if anything changes.

We are seeing an improvement in message processing times. This is likely due to lower traffic levels during off-peak hours in Germany. Microsoft continues to investigate the issue. At this time, the problem remains isolated to EOP servers located in the Frankfurt region. Thank you for your patience. We’ll provide another update in 3 hours or sooner if anything changes.

Microsoft reports in EX1331830 that Exchange Online users may experience significant delays or failures when sending and receiving email messages in Exchange Online, with some messages remaining undelivered for over an hour. The impact is currently limited to users in North America and Germany (although we do not see these delays in North America). Microsoft is continuing to analyze the issue and determine next steps. This confirms this is not a CodeTwo infrastructure issue. At the same time, we are observing a significant improvement in server-side mail processing performance in Germany for all CodeTwo users in this region. Queues are now nearly cleared. We continue to monitor the situation. All signatures are added correctly. Thank you for your patience. We’ll provide another update in 3 hours or sooner if anything changes.

Microsoft reports in EX1331830 that they are now evaluating targeted service infrastructure resets as a potential mitigation and they're collecting additional diagnostic data to determine the next steps. We continue to observe stable mail flow performance in the Germany West Central region, with no delays in other regions. All signatures are added correctly. We’ll continue to monitor the situation and provide another update in 3 hours or sooner if anything changes.

Microsoft reports in EX1331830 that their configuration changes have reached approximately 50% of the affected infrastructure and message queues are steadily improving. This is also confirmed by our telemetry. More information can be found in the Microsoft 365 Admin Center under EX1331830 (https://admin.cloud.microsoft/#/servicehealth/:/alerts/EX1331830), if accessible. CodeTwo is and has been operating normally throughout this incident. All emails were delivered with signatures attached. As the issue is no longer affecting our mail flow and is not related to CodeTwo infrastructure, we are resolving it. Our teams will continue to monitor the situation 24/7/365.

We’re investigating an issue affecting email delivery for messages processed by CodeTwo services to apply email signatures. We’re also checking whether this may be related to an Azure DNS problem. Please stay tuned for further updates.

We’re seeing indications that Azure DNS issues could have affected email flow for some customers using CodeTwo services. DNS appears to be ok again, and several previously affected customers have already confirmed successful email delivery. We’re continuing to investigate to rule out any other causes. No configuration changes or updates were made to our services today.

Microsoft has acknowledged the issue after receiving reports from multiple organizations. They are investigating on their side as well, but the root cause has not yet been identified. On our side, we are no longer receiving additional reports and all systems appear to be operating normally, but we’ll continue to monitor the situation and carry on with our investigation.

It looks like the issue is no longer occurring, but we are continuing to monitor the situation and are still investigating the root cause. Here’s a quick summary of events: 1. Some of our mail processing servers were temporarily unreachable, most likely due to an Azure DNS outage. As a result, some emails sent by our customers (using the cloud-mode for signatures) were rejected with a bounce‑back (NDR) by Exchange Online because our mail processing domain could not be resolved at that moment. 2. Some emails still went through. This happened either because they did not hit the Azure DNS issue (not all messages were affected), or because they were queued by Exchange Online for delivery and Azure DNS came back online before the system generated an NDR. 3. Once DNS became available again, our domain was visible and queued messages could be delivered normally. 4. Nothing in this incident occurred within CodeTwo’s systems. The issue happened entirely before any message reached our service pipeline, which is why our service logs did not show any abnormalities. 5. Emails that did not generate an NDR (did not bounce back) can be assumed to have been delivered successfully. Emails that generated an NDR (bounced back) will need to be resent by the original senders. We are continuing to investigate this issue with Microsoft (who has now confirmed the Exchange Online infrastructure experienced an issue) and are trying to determine why Azure DNS became unavailable for a short period. We'll let you know about the results of that investigation. All CodeTwo services are operating normally.

We have confirmed that the situation has returned to normal, and Microsoft has acknowledged that the issue originated on the Microsoft 365 side. For now, we are closing this incident, but our 24/7/365 Monitoring Team will continue to keep a close eye on the service. We will share more details in the post‑mortem once Microsoft provides us with their RCA.

# Summary On March 18, 2026, a small subset of CodeTwo customers experienced temporary issues with email delivery. The incident was caused by a Microsoft networking and DNS‑related issue within Microsoft 365 infrastructure and was not the result of a failure in the CodeTwo service. # Impact * Only a limited number of customers were affected. * The issue occurred intermittently. * The impact was limited to customers whose mail flow depended on Microsoft 365 services affected by the incident. # Root cause Microsoft confirmed that the incident \(ID MO1255228\) was caused by a temporary issue with their networking infrastructure, where part of the infrastructure intended to handle production traffic was only partially reinstated. This led to DNS and load‑balancing issues, affecting services such as Exchange Online. The incident originated entirely within Microsoft’s infrastructure and was outside of CodeTwo’s control. # Resolution Microsoft manually reinstated the full networking infrastructure and confirmed service health recovery. Following this action, telemetry indicated stable and healthy service operation. # Why CodeTwo was affected CodeTwo services integrate directly with Microsoft 365 and Azure and rely on Microsoft‑managed DNS and networking components. DNS failures at the Microsoft platform level affect all services integrated with Microsoft 365, including third‑party solutions. There is no technically viable way for any Microsoft 365-integrated service to be fully immune to platform‑level DNS or networking failures on Microsoft’s side. # Preventive measures * CodeTwo services are monitored 24/7/365. * We operate redundant and failover‑capable infrastructure. * In case of Microsoft‑side incidents, we take all actions within our control to minimize customer impact, including traffic rerouting where technically possible. Microsoft stated that this type of incident has been extremely rare and committed to improving safeguards to prevent similar events in the future. # Current status Microsoft has confirmed that the affected services were fully restored and operating normally. No further issues related to this incident have been observed.