Company Logo

Is there an Templafy outage?

Templafy status: Systems Active

Last checked: 6 minutes ago

Get notified about any outages, downtime or incidents for Templafy and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Templafy outages and incidents

Outage and incident data over the last 30 days for Templafy.

There have been 1 outages or incidents for Templafy in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for Templafy

Outlogger tracks the status of these components for Xero:

Email Signature Server 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
Public API Active
WebApp Active
Component Status
Active
Email Signature Server Active
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
Active
Public API Active
WebApp Active

Latest Templafy outages and incidents.

View the latest incidents for Templafy and check for official updates:

Updates:

  • Time: July 26, 2023, 2:48 p.m.
    Status: Postmortem
    Update: On July 25, 2023, starting at 9:41 AM CET, a small subset of our customers hosted on Prod0 in West Europe with the Spaces module enabled encountered a critical issue that prevented them from navigating the asset explorer folder structure. This issue was first detected via internal usage at 10:35 AM CET. The code causing the bug was identified, reverted and a fix was deployed at 12:12 PM CET
  • Time: July 25, 2023, 11:59 a.m.
    Status: Resolved
    Update: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
  • Time: July 25, 2023, 10:11 a.m.
    Status: Monitoring
    Update: The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.
  • Time: July 25, 2023, 9:43 a.m.
    Status: Identified
    Update: We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.
  • Time: July 25, 2023, 8:59 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: July 12, 2023, 8:05 a.m.
    Status: Postmortem
    Update: On July 10, 2023, starting at 10:14 PM CET, we experienced a service interruption that affected some customers in Australia due to a misconfiguration in our Email Signature Server release pipeline. This resulted in temporary unavailability for a subset of customers. We have taken immediate action to address the issue and prevent similar incidents in the future. Our measures include enhancing configuration validation, improving testing procedures and strengthening monitoring capabilities. The incident was successfully mitigated at 11:42 PM CET. We sincerely apologize for any inconvenience caused and appreciate your patience.
  • Time: July 11, 2023, 7:27 a.m.
    Status: Resolved
    Update: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
  • Time: July 11, 2023, 6:55 a.m.
    Status: Monitoring
    Update: The incident has been successfully mitigated for the affected customers. Our team is actively monitoring the situation to ensure ongoing stability. We are observing the systems to prevent any further disruptions.
  • Time: July 11, 2023, 6:53 a.m.
    Status: Identified
    Update: We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.

Updates:

  • Time: July 4, 2023, 9:22 a.m.
    Status: Postmortem
    Update: On July 4, 2023, starting at 9:27 AM CET, users provisioned in WestEurope Prod 0 encountered a critical issue that prevented them from creating documents. This incident was attributed to an internal misconfiguration within the system. Following engineering investigation and troubleshooting, the internal misconfiguration was identified and subsequently reverted. This resolution action effectively restored the document creation functionality for all affected users. The incident was successfully resolved at 11:15 AM CET.
  • Time: July 4, 2023, 9:17 a.m.
    Status: Resolved
    Update: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
  • Time: July 4, 2023, 8:08 a.m.
    Status: Identified
    Update: We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.
  • Time: July 4, 2023, 8:07 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: June 9, 2023, 9:29 a.m.
    Status: Postmortem
    Update: On May 6th, at 9:41 CEST, a subset of Templafy customers began experiencing difficulties with Stuf DCR, our service. We sincerely apologize for any inconvenience caused by this issue. The problem originated from the loss of STUF DCR certificate configuration, which occurred due to an unintended out-of-order execution of data and schema migrations. This unexpected sequence of events resulted in the configuration being overwritten or disrupted, leading to service disruptions and errors for our affected customers. As soon as we became aware of the issue at 9:41 CEST, our team promptly initiated an investigation to identify the root cause and find a resolution. By 03:43 CEST, we were able to successfully restore the lost data and rectify the underlying problem. During the restoration process, we closely monitored the situation to ensure that requests were being processed correctly. We are pleased to inform you that normal operations have resumed, and we are now observing successful requests being handled without any issues. We deeply regret any inconvenience or disruption this incident may have caused for our valued customers. We understand the importance of reliable and uninterrupted service, and we are committed to implementing measures to prevent similar occurrences in the future. Thank you for your patience and understanding throughout this situation.
  • Time: June 5, 2023, 1:42 p.m.
    Status: Resolved
    Update: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
  • Time: June 5, 2023, 1:09 p.m.
    Status: Monitoring
    Update: The incident has been successfully mitigated, and our team is actively monitoring the situation to ensure ongoing stability and performance. We are observing the systems to prevent any further disruptions.
  • Time: June 5, 2023, 12:28 p.m.
    Status: Identified
    Update: Engineers have implemented the fix and currently are working on validating it. Further updates will be posted here soon.
  • Time: June 5, 2023, 10:13 a.m.
    Status: Identified
    Update: We have identified an issue that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.
  • Time: June 5, 2023, 9:42 a.m.
    Status: Investigating
    Update: We are currently investigating the issue.

Updates:

  • Time: June 7, 2023, 5:58 a.m.
    Status: Postmortem
    Update: A deployment at 8:02 CEST on the 1st of June caused data inconsistencies resulting in an outage for data connectors relying on certificate authentication. This affected only customers in West Europe \(Prod0\) region. The problem was first noticed by Templafy at 8:04 and reported by customers at 8:25 CEST. The incident was resolved at 11:30 CEST. Moving forward, steps will be taken to ensure that the data remains consistent, identifiers are unique, and better monitoring is in place to prevent similar incidents from happening again.
  • Time: June 1, 2023, 9:35 a.m.
    Status: Resolved
    Update: The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.
  • Time: June 1, 2023, 8:15 a.m.
    Status: Identified
    Update: We have identified an issue related to a subset of our connectors and are working towards a resolution. The incident affects only customers in West Europe (Prod0) region. Further updates will be posted here soon.

Check the status of similar companies and alternatives to Templafy

Docusign
Docusign

Systems Active

PandaDoc
PandaDoc

Systems Active

Foxit
Foxit

Systems Active

Nitro Sign
Nitro Sign

Systems Active

Documoto System

Systems Active

SmartSuite
SmartSuite

Systems Active

Frequently Asked Questions - Templafy

Is there a Templafy outage?
The current status of Templafy is: Systems Active
Where can I find the official status page of Templafy?
The official status page for Templafy is here
How can I get notified if Templafy is down or experiencing an outage?
To get notified of any status changes to Templafy, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Templafy every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Templafy do?
Templafy streamlines document creation for 800+ global organizations, reducing risk and boosting productivity through automation.