Time: Sept. 13, 2022, 7:53 a.m.

Status: Postmortem

Update: The 7th of September around 17:30 CEST a subset of users started experiencing problems to authenticate with the application. This was due to a code change that introduced a bug which caused external user groups to be incorrectly validated. The issue affected only users who belonged to external user groups which had a display name shorter than 3 characters. This was quickly identified by our engineering team and a fix was created and deployed to the single affected environment, West Europe region\(Production 0\). All other production environments were not affected. The issue was confirmed to be fixed at 19:44 CEST.

Time: Sept. 7, 2022, 5:44 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: Sept. 7, 2022, 3:36 p.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: Sept. 9, 2022, 8:14 a.m.

Status: Postmortem

Update: The 30-th of August around 10 AM CEST multiple Microsoft services started failing as a result of a system upgrade. One of the Microsoft services affected was Azure Kubernetes Service, which we use as the platform to run the Templafy Hive Application. As a result of this failure, our Admin center in one of our West Europe regions\(prod1\) experienced service interruptions. As soon as Microsoft publish a remediation solution this was applied to the affected Azure Kubernetes Service and the functionality fully recovered. More details about this can be found on the [Azure status page.](https://status.azure.com/en-gb/status/history/#:~:text=Preliminary%20Post%20Incident%20Review%20(PIR)%20%2D%20Canonical%20Ubuntu%20Issue%20Impacted%20VMs%20and%20AKS%20(Tracking%20ID%202TWN%2DVT0))

Time: Aug. 30, 2022, 12:15 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: Aug. 30, 2022, 10:06 a.m.

Status: Identified

Update: Microsoft has confirmed that there is an issue with several of its services, including the AKS service. We have identified this service outage as the root cause of this incident. These are the details from the Microsoft incident: "Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors - Investigating Starting at approximately 06:00 UTC on 30 Aug 2022, a number of customers running Ubuntu 18.04 (bionic) VMs recently upgraded to systemd version 237-3ubuntu10.54 reported experiencing DNS errors when trying to access their resources. Reports of this issue are confined to this single Ubuntu version. This bug and a potential fix have been highlighted on the Canonical / Ubuntu site, which we encourage impacted customers to read: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119 An additional potential workaround customers can consider is to reboot impacted VM instances so that they receive a fresh DHCP lease and new DNS resolver(s). If you are running a VM with Ubuntu 18.04 image, and you are experiencing connectivity issues, we recommend you evaluate the above mitigation options. If you are not experiencing impact on your Ubuntu 18.04 images, but you have unattended security updates enabled, we recommend you review this setting until the Ubuntu issue is mitigated. The next update will be provided in 4 hours, or as events warrant. This message was last updated at 09:56 UTC on 30 August 2022" Source:https://status.azure.com/en-gb/status

Time: Aug. 30, 2022, 8:55 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: Aug. 25, 2022, 7:58 a.m.

Status: Postmortem

Update: On the 17-th of August around 3 AM CET time one of the Microsoft services that our application is relying on for queue based communication started to fail. This affected the processing of all new documents and the creation of new tenants in one of our Europe environments. The problem was remediated by Microsoft around 10:15 CET time, after which the pending documents got processed, also tenant creation and new document processing became fully operational again.

Time: Aug. 17, 2022, 9:01 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: Aug. 17, 2022, 7:10 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 21, 2022, 12:59 p.m.

Status: Postmortem

Update: Microsoft had issues with Azure SQL service \(starting at 05:38 CET July, 21st\). Because of this, users had intermittent issues accessing Templafy Hive. Microsoft started to mitigate the issue with Azure SQL service at 10:24 AM CET, after which Templafy Hive was fully operational. More info on the Azure status page about the incident [Azure status](https://status.azure.com/en-gb/status/history/#:~:text=Post%20Incident%20Review%20(PIR)%20%2D%20SQL%20Database%20%2D%20West%20Europe%20(Tracking%20ID%203TBL%2DPD8))

Time: July 21, 2022, 8: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 21, 2022, 7:47 a.m.

Status: Identified

Update: MIcrosoft has initiated a mitigation procedure for this issue and we are monitoring the status of this mitigation

Time: July 21, 2022, 5:42 a.m.

Status: Identified

Update: From initial investigations we have concluded that Templafy is being affected by an Azure Service issue already identified and reported by Microsoft Microsoft is currently investigating the issue and we are monitoring the status.

Time: July 21, 2022, 5:30 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 6, 2022, 12:01 p.m.

Status: Postmortem

Update: At 4th of July 2022 at 07:30 AM CET a faulty database migration had been rolled out, which cause multiple email signature parts to be disabled. Because of this email signatures of several tenants were disabled completely. Engineers were engaged on 4th of July 2022 at 11:21 AM CET and started to investigate the issue and as soon as the root cause was found, Engineers started to implement a fix to the problem. On 4th of July 2022 at 16:20 PM CET Engineers had rolled out the fix to all clusters and this re-enabled the email signature parts that had been accidentally disabled.

Time: July 4, 2022, 2:16 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: July 4, 2022, 11:26 a.m.

Status: Identified

Update: Engineers have investigated and have found the root cause of the problem. They are currently working on a resolution of the problem.

Time: July 4, 2022, 9:47 a.m.

Status: Identified

Update: We have identified an issue with Email Signatures that affects a subset of customers and are working towards a resolution. Further updates will be posted here soon.