https://approjects-vendor-status-watch.static.hf.space/v/codetwo.htmlIncidents from CodeTwo's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/293bgbjmm3hpcodetwo:2026-06-02T12:39:33.471ZTue, 02 Jun 2026 12:39:33 +0000Microsoft 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.https://stspg.io/qrdqf2qrs3mccodetwo:2026-03-18T15:41:44.952ZWed, 18 Mar 2026 15:41:44 +0000# 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 servihttps://stspg.io/8x7t2gw6dngkcodetwo:2026-02-07T08:56:21.991ZSat, 07 Feb 2026 08:56:21 +0000This incident has been resolved.https://stspg.io/1jl9c6r2gqt8codetwo:2026-01-22T19:37:29.383ZThu, 22 Jan 2026 19:37:29 +0000The fix implemented by the MS Exchange Online team worked and our service is fully operational again. The most recent update from Microsoft: "We’re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services."https://stspg.io/j0fb5d4lznf2codetwo:2026-01-12T12:17:56.421ZMon, 12 Jan 2026 12:17:56 +0000This incident has been resolved.https://stspg.io/6ns33d3wh0sqcodetwo:2025-11-06T09:26:06.194ZThu, 06 Nov 2025 09:26:06 +0000Microsoft has published official information about this incident on the Service Health Dashboard (SHD) under ID: EX1183800. Please refer to the SHD for more details. Since this officially confirms that the issue was not related to CodeTwo, we are resolving this incident on our end. If you have any questions, please raise a service request with Microsoft. You are also welcome to contact our Support Team at: https://www.codetwo.com/company/contact. All CodeTwo services have been operational during the incident. Thank you for your understanding and cooperation.https://stspg.io/61c3w7hg0x2zcodetwo:2025-10-29T16:14:43.799ZWed, 29 Oct 2025 16:14:43 +0000The issue appears to be resolved now. A bunch of guys were about to turn blue (when we realized Microsoft has messed up the DNS configuration) - we're breathing again. Thank you for your patience and understanding! This was a widespread incident affecting multiple Microsoft resources worldwide. Some of the performance issues we experienced as a result were unavoidable. Nevertheless, we’ll continue to enhance our high availability capabilities to make our are services more resilient to similar problems in the future. Please stay tuned, and thank you for your continued trust and business. If you have any questions or need assistance, please reach out to our Customer Success Team - we’re online 24 hours a day. And yes, our SOC Team also works around the clock, continuously monitoring our https://stspg.io/px7zf49lly1ycodetwo:2025-10-09T10:29:20.588ZThu, 09 Oct 2025 10:29:20 +0000This incident has been resolved.https://stspg.io/y88l988zhb1fcodetwo:2025-09-15T23:08:10.073ZMon, 15 Sep 2025 23:08:10 +0000It looks like the incident affected only a handful of tenants in Australia East, and the overall impact was very limited and not related to CodeTwo. We’re not seeing any issues with our services, so we’re closing this incident. Our 24/7/365 Proactive Monitoring Team will continue to actively monitor the service. If you are experiencing any problems, please feel free to reach out to our Support Team - we’re available around the clock.https://stspg.io/4sbrm6b88m69codetwo:2025-08-29T13:01:45.195ZFri, 29 Aug 2025 13:01:45 +0000The problem has been resolved by Microsoft. For further information, please check Service health in the Microsoft 365 Admin Center (Incident ID: EX1144276). CodeTwo is operating and has been operating normally. All emails were delivered with signatures attached.https://stspg.io/x3zy3s3pjjd3codetwo:2025-08-25T05:32:25.391ZMon, 25 Aug 2025 05:32:25 +0000This incident has been resolved.