Templafy incident
Service degradation - Issues accessing Templafy One
Templafy experienced a critical incident on April 21, 2025 affecting WebApp, lasting 12h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 21, 2025, 07:00 PM UTC
We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.
- identified Apr 21, 2025, 07:25 PM UTC
We have identified an issue that affects all Templafy One customers. The first investigation points to specific Azure Services being degraded and this is causing Templafy One to be down. We are working with Microsoft towards a resolution. Further updates will be posted here soon.
- monitoring Apr 21, 2025, 09:07 PM UTC
The incident has been successfully mitigated as a result of the Azure services coming back online, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.
- resolved Apr 22, 2025, 07:21 AM UTC
The incident has been resolved, and all Azure services are now operating normally. A detailed postmortem will be shared shortly. We apologize for the disruption and appreciate your patience.
- postmortem Apr 22, 2025, 08:29 AM UTC
Incident Initiation At 8:29 PM CET on April 21, 2025, an issue was identified impacting availability of our Templafy One application hosted on Azure App Services in the North Europe region. The issue resulted in connectivity drops for end users, causing temporary disruptions in service. The incident was attributed to unplanned maintenance initiated by Azure without prior notice. Investigation Upon noticing the service disruptions, the engineering team began monitoring the application and associated Azure resources. Logs and metrics indicated availability drops aligning with the start time of the incident. Further investigation confirmed that the root cause was an unplanned hotfix applied by Azure App Services, as communicated in an official Microsoft Azure service notification \(Tracking ID 1VZN-PBG\). The maintenance activity began shortly after 7:00 PM CET on April 21, 2025 and was performed during non-business hours. Mitigation and Resolution No action was required from our side as the issue was caused by Azure infrastructure maintenance. The event concluded at 10:58 PM CET on April 21, 2025, with all services stabilizing post-maintenance. The application automatically recovered once the underlying Azure App Services instances resumed normal operation. Impact and Scope The incident was limited to Templafy One. User Experience: Users may have experienced temporary unavailability or connectivity interruptions during the maintenance window between 8:29 PM and 10:58 PM CET.