CodeTwo incident
Degraded performance of the Admin Panel and other apps due to Azure disruptions
CodeTwo experienced a minor incident on October 9, 2025 affecting Signature management (app.codetwo.com) and Signature management (app.codetwo.com) and 1 more component, lasting 7h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 09, 2025, 10:29 AM UTC
Some of our apps - such as the Admin Panel and the Manage Signatures App - may experience degraded performance, including slow loading times or failure to load entirely. This issue is due to widespread disruptions affecting Microsoft 365 and Azure services. You can track updates via https://x.com/MSFT365Status/status/1976221477859983782 or https://status.cloud.microsoft, although the latter may also be intermittently unavailable as it's hosted by Microsoft. Microsoft has identified its Front Door services as the likely cause, which is also impacting standard Microsoft 365 users. We are actively monitoring the situation on our end. Despite the app loading issues, email signatures continue to be appended correctly, and mail delivery remains unaffected.
- identified Oct 09, 2025, 10:41 AM UTC
We’re seeing that the Azure Front Door Services issues are now also affecting users in the UK and UAE regions. As a result, Microsoft 365 users in these areas may experience intermittent login issues when accessing their M365 resources. Some CodeTwo apps - also hosted on Azure - may be impacted as well, due to the widespread nature of the disruption. Important Reminder: All email signatures are being appended as expected, and we are not observing any issues with mail delivery at this time. You can follow updates on this Microsoft incident via: https://x.com/MSFT365Status/status/1976221477859983782 https://status.cloud.microsoft (Note: this page may also be intermittently unavailable)
- monitoring Oct 09, 2025, 01:17 PM UTC
Microsoft has recovered most of affected resources. We are monitoring the results.
- resolved Oct 09, 2025, 05:37 PM UTC
This incident has been resolved.