The incident began on March 12, 2026, at 10:17 AM CET, when some users attempting to access 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.
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.
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 from mobile devices without issues.
This incident affected users attempting to access 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:
Users accessing the service from mobile devices connected to these clusters may have experienced difficulty loading the site during the incident window.
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.