Issues when accessing Templafy

Update timeline

1. identified Mar 12, 2026, 01:08 PM UTC

   We have identified an issue that affects a subset of customers on West Europe (Production0), Australia East (Production 3), West Europe (Production5) and are working towards a resolution. Further updates will be posted here soon.

2. monitoring Mar 12, 2026, 01:20 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 12, 2026, 02:50 PM UTC

   The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

4. postmortem Mar 16, 2026, 02:28 PM UTC

   # Investigation The incident began on March 12, 2026, at 10:17 AM CET, when some users attempting to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices experienced difficulties loading the site. The issue was detected at 1:36 PM CET, after reports indicated that the site could not be accessed successfully from certain mobile clients. The engineering team began investigating immediately after detection. The issue was related to an ongoing infrastructure change where traffic was gradually being moved from the current routing component to a new one. During this transition, a configuration difference in the new system caused some requests to be rejected. This issue mainly affected users accessing the service from mobile devices. # Mitigation Once the cause was identified, the engineering team mitigated the issue by redirecting traffic back to the previous routing component. This rollback restored the previous routing behavior and prevented further request validation conflicts, allowing the team to continue analyzing the routing component configuration. # Resolution The incident was resolved on March 12, 2026, at 2:31 PM CET, once traffic had been fully reverted to the previous infrastructure configuration. Following the rollback, affected users were again able to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices without issues. # Impact and Scope This incident affected users attempting to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices during the migration window on March 12, 2026. The issue occurred during a controlled infrastructure migration and impacted requests routed through the following clusters: * West Europe \(Production 0\) * Australia East \(Production 3\) * West Europe \(Production 5\) Users accessing the service from mobile devices connected to these clusters may have experienced difficulty loading the site during the incident window. # Post-Incident Actions Following the incident, the engineering team reviewed the migration process and identified improvements to the procedures used during infrastructure transitions. These improvements will help ensure smoother migrations and reduce the likelihood of similar issues occurring in the future.