Is there an Templafy outage?
Templafy status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes 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 28th of November at 11:39 CET, we had an outage in our European cluster that affected all tenants. The cause was an error in the SQL server database. The initial mitigation strategy included increasing the database capacity which restored normal operational behavior by 12:10 CET. From there, the investigation continued to determine the root cause of the issue. We have reached out to Microsoft and involved them to assist in the matter. Conclusions from the investigation are that the SQL server completed an automated update statistics process to determine the optimal execution plan for a particular query. The limited sample size used for this process led the SQL server to decide to run it in a different way. This caused queries to take more time and resources to reach capacity leading to the incident. To make sure this issue does not happen again, we are implementing changes so the sampling for this procedure is set at an appropriate level.
Status: Postmortem
Impact: Critical | Started At: Nov. 28, 2022, 11 a.m.
Description: Starting on Monday the 24th of October at 15:27 CEST, users with email signature web add-in that used Outlook Desktop began experiencing issues loading signatures. Tenants in all environments were affected. The issue was caused by a reference to an office library in an incorrect context. The fix was released at 16:50 CEST. Additionally, as the behavior is not specifically described in the supplier documentation, we have raised this as an issue with the supplier. The Templafy Team will document the unexpected behavior in internal records until adequate documentation is provided by the supplier.
Status: Postmortem
Impact: Major | Started At: Oct. 24, 2022, 1:27 p.m.
Description: Starting at 12th September 2022 11:14 AM CET a small group of users could not login to Templafy. The engineering team investigated the issue and discovered that it was introduced in a recent change where the character limitation for the display name for external groups has been increased from 100 to 120 characters and added validation to the external group display name to have 120 characters. Users that was a part of an external group where the display name is more than 120 characters failed to login because the validation did not allow more than 120 characters. The engineering team analyzed all existing external group display names and increased the character limitation to satisfy the current data set and that solved the issue at 12th September 2022 5:00 PM CET.
Status: Postmortem
Impact: Major | Started At: Sept. 12, 2022, 12:39 p.m.
Description: Starting at 8th September 2022 2:18 AM CET customers in US East experienced emails sending outside organization failed. A misbehavior in the email sending marked the IP address, used to send emails, as blocked by Microsoft. We noticed the issue at 8th September 9:41 PM CET from a customer report. The engineering team started working on the issue at 9th September 2022 12:04 AM CET and used Microsoft delist service to unblock the IP address. The delisting should be escalated within 30 minutes as Microsoft claims, however Microsoft did not respond within this timeframe. The engineering team created support tickets for Microsoft to speed up the unblock process, but actions were taken until 9th September 8:50 AM CET where we got a call from Microsoft that the IP address is not blocked anymore. The engineering team already noticed that the issue faded 9th September 7:04 AM CET from our logs before Microsoft responded. To prevent the issue from happening again, the engineers have created a plan to move away from IP address based email sending.
Status: Postmortem
Impact: Critical | Started At: Sept. 8, 2022, 11 p.m.
Description: The 8th of September around 8 CEST a subset of users started experiencing problems accessing the application. This was due to a bug introduced with a database change in our UserManagement service. The databases changes caused performance issues, requiring extensive resources to be able to query the records. This lead to CPU exhaustion on the database causing all queries to fail, making the application inaccessible. Around 11 CEST the engineering team found the root cause of the issue and deployed a fix. After the fix was applied the CPU utilization dropped and the application was fully accessible again. The issue affected only the West Europe region\(Production 1\). All other environments were not affected.
Status: Postmortem
Impact: Major | Started At: Sept. 8, 2022, 6:14 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.
