Is there an Templafy outage?
Templafy status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Templafy.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Templafy Email Signature Server | Active |
| Email Signature Server | Active |
| Templafy Hive | Active |
| Account Management | Active |
| Add-in Management | Active |
| AI Assistant | Active |
| Authentication | Active |
| Email Signature | Active |
| Engage | Active |
| Integrations | Active |
| Library & Dynamics | Active |
| Productivity | Active |
| Resource Management | Active |
| User Management | Active |
| Templafy One | Active |
| Public API | Active |
| WebApp | Active |
View the latest incidents for Templafy and check for official updates:
Description: On May 27, 2024, at 10:06 CET, an issue impacting users in the West Europe \(Production 0\) environment was identified. The issue caused users of West Europe \(Production 0\) to experience errors and slow responses when accessing the application. The engineering team quickly discovered that the problem was caused by a faulty database migration and immediately started to implement a fix. By 10:57 CET, the fix was implemented and deployed to our West Europe \(Production 0\) environment. This resulted in the application working correctly again. After the engineering team closely monitored the application and confirmed that it was working with the desired parameters, the issue was resolved at 16:19 CET. We apologize for the disruption and remain committed to ensuring the reliability and stability of our services.
Status: Postmortem
Impact: Minor | Started At: May 27, 2024, 8:06 a.m.
Description: On May 22, 2024, at 4:58 PM CET, an incident impacting all customers using the Productivity Add-in within the Insider track using the Hive environment was triggered by a code change introducing a bug in PowerPoint, causing errors and numerous popup messages when users attempted to work with tables. Upon detection, the engineering team swiftly initiated an investigation and identified the issue by 5:03 PM CET on May 22. To mitigate the impact, the team promptly executed a plan to downgrade affected users to a previously stable version, completing the action by 5:26 PM CET on May 22. We apologize for the disruption and remain committed to ensuring the reliability and stability of our services.
Status: Postmortem
Impact: Minor | Started At: May 22, 2024, 3:08 p.m.
Description: `On May 8, 2024, at 4:00 PM CET, an incident began with the Templafy Desktop upgrade, which resulted in broken AddIns for a limited set of customers. This issue was detected, on May 8, 2024, at 12:00 PM CET. The engineering team promptly began investigating the incident at 4:07 PM CET on May 8, 2024. They worked to determine the scope of affected customers by testing various versions of the Templafy Desktop Host. By 4:38 PM CET, the team had identified and deprecated the problematic Templafy Desktop Client version to prevent further customer upgrades. By 4:52 PM CET, the incident status had moved into the mitigation phase. For customers already impacted, the team identified two solutions: reinstalling Templafy Desktop or removing the content of Templafy Desktop Client versions and restarting Templafy Desktop. These solutions were communicated to the relevant individual customers. To prevent the issue from happening again, we will fix the root cause and implement further testing between version upgrades.`
Status: Postmortem
Impact: Major | Started At: May 8, 2024, 2:22 p.m.
Description: On the 24-th of April at 9:05 CET an incident occured that affected users using our West Europe \(Production 1\) cluster. The incident resulted from an execution plan update of the SQL Server, causing queries to execute without utilizing the appropriate database index. Consequently, queries on the UserManagement database experienced high resource consumption, leading to severe slowdowns and eventual inaccessibility, causing the application on the West Europe \(Production 1\) cluster to become inaccessible. At 9:41 CET mitigation was achieved by scaling up SQL Server resources. Currently, the engineering team is actively investigating solutions to prevent similar incidents in the future.
Status: Postmortem
Impact: Critical | Started At: April 24, 2024, 7:32 a.m.
Description: On April 22, 2024, at 10:46 AM CET, an issue was reported affecting all users across every cluster, where the dialog for creating or updating documents, containing TextElement or SlideCollection insertions, would not advance beyond the loading screen on subsequent attempts. Initial investigations quickly linked the problem to a recent update in the UserManagement Microfrontend, specifically a defect introduced in the UserProfile component. This issue was rectified by reverting the changes, with normal functionality restored by 2:05 PM CET on the same day. In response to this incident, we have implemented more rigorous testing procedures for frontend components and expanded end-to-end testing to better simulate user interactions. We've also revised the integration and usage of the UserProfile component to prevent recurrence and introduced new tests that run asynchronously to detect issues early without delaying other processes. We apologize for the inconvenience caused and are committed to continuous improvements to ensure the reliability of our services.
Status: Postmortem
Impact: Major | Started At: April 22, 2024, 9:16 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
