Templafy Outage History

22 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Templafy status100.00% uptime history

Every Recorded Templafy Incident

Templafy incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Customers using Zscaler might experience issues with multiple functionalities due to blocked QUERY request## Investigation On October 28, 2026, at 3:11 PM CET an issue was detected, following reports from affected customers. The engineering team investigated the reported behavior and identified that a recent migration to…5h 51mResolved
Sep 29, 2026Document agents not responding in West Europe (Production 0), West Europe (Production 1) and West Europe (Production 5)# Investigation On September 29, 2026, at approximately 12:03 PM CET, an upstream Microsoft Azure platform issue began affecting services supporting Document Agents. Customers experienced Document Agents not responding…1h 56mResolved
Sep 8, 2026Service degradation - Customers might experience issues with the Find Template and Update Document functionality in the Word VSTO Add-ins.## Investigation A small number of users across two tenants reported issues when using **Find Template** and **Update Document** in the VSTO add-in. The engineering team investigated the reported behavior and reviewed…23h 45mResolved
Aug 14, 2026Service degradation - Potential Issues Updating Word Documents in VSTO Add-ins**Investigation** The incident began at 11:19 AM CET on August 12, 2026, following the promotion of Office VSTO add-ins version 7.3.220 to the stable release channel. The issue was detected at 10:25 PM CET on August…25 minResolved
Jun 24, 2026Transient errors in West Europe (Production 0) and West Europe (Production 5)**Investigation** On **June 24, 2026**, 2:54 PM CET the engineering team identified an issue affecting the gateway infrastructure responsible for routing customer traffic. As a result, some requests were directed to…1h 47mResolved
Jun 8, 2026AI Services are impacted by an Azure Open AI services incident# Investigation On June 8, 2026, at 10:01 AM CET, the engineering team became aware of delays and intermittent failures affecting AI-powered functionality within Document Agents, including outline preparation and…7h 0mResolved
Apr 1, 2026Document creation services 1.1 connector is not generating documents**Investigation** On April 1, 2026, a subset of customers began reporting issues when attempting to open or generate documents through app connectors. As a result, an incident was created at 10:58 AM CET. The…25h 47mResolved
Mar 31, 2026Intermittent issues accessing Templafy - West Europe (Production 0)**Investigation** On March 31, 2026, at 12:02 PM CET, an issue began affecting access to Templafy for some customers hosted in West Europe \(Production 0\). The issue was detected at 12:09 PM CET through system alerts…1h 55mResolved
Mar 12, 2026Issues when accessing Templafy# Investigation The incident began on March 12, 2026, at 10:17 AM CET, when some users attempting to access [templafy.templafy.com](http://templafy.templafy.com) from mobile devices experienced difficulties loading the…1h 42mResolved
Mar 10, 2026Service degradation - Unable to create documents## Investigation The incident began on March 10, 2026, at 8:04 AM CET and affected document generation and download functionality for some users. In certain cases, documents could fail to generate when templates…1h 19mResolved
Mar 9, 2026Update presentation is not working for any PowerPoint presentation# Investigation The incident began on March 5, 2026, at 8:04 AM CET and affected the Document Updater functionality for PowerPoint presentations, where users encountered an error when attempting to update…2h 17mResolved
Mar 4, 2026Assets are not visible in new experience West Europe (Production 0)# Investigation The incident began on March 4, 2026, at 8:04 AM CET, when Templafy assets were not visible in the new end-user experience within the Hive environment. The issue affected users attempting to access…38 minResolved
Feb 24, 2026Library insight admin area not rendering# Investigation On February 23, 2026, at 11:00 AM CET, an issue was introduced affecting specific pages within the Library Insights section of the platform. The issue impacted administrators attempting to access…2h 12mResolved
Feb 20, 2026Service degradation - Failure to request Public API (Production 0)**Investigation** The issue began on February 20, 2026, at 11:42 AM CET in the Hive environment on West Europe \(Production 0\), where public API requests started failing due to an authentication problem. The incident…53 minResolved
Feb 18, 2026Service degradation - Admins may experience issues when loading Library Insights**Investigation** On February 17, 2026, at 11:26 PM CET, we detected an issue where the Library Insights feature in the Hive environment began timing out. The issue affected administrators with space owner permissions…1h 58mResolved
Feb 9, 2026Users encounter issues when accessing West Europe (Production 1)# Investigation On February 9, 2026, at 8:19 AM CET, an issue began affecting the database. The incident was detected shortly after at 8:22 AM CET, when automated monitoring raised an alert indicating that database CPU…7h 57mResolved
Jan 29, 2026Document Agents and AI Assistant Service Degradation**Investigation** The issue was detected at 12:14 PM CET on January 29, 2026, when Document Agents and AI Assistant services began experiencing degraded performance across the West Europe production environments…2h 51mResolved
Jan 29, 2026Service degradation - Content Library is not accessible in West Europe (Production 0)**Investigation** The issue began at 11:05 AM CET on January 29, 2026, following a deployment to West Europe \(Production 0\). From that point, some users were unable to access the content library in both the Web…41 minResolved
Jan 27, 2026Document Agents and Ai Assistant Service Degradation_**Investigation**_ The issue was detected at 10:22 AM CET on January 27, 2026, when Document Agents and AI Assistant services began experiencing degraded performance across the West Europe production environments…9h 0mResolved
Dec 17, 2025Degraded performance detected on West Europe (Production 1)**Investigation** The incident began on December 17, 2025, at 9:19 AM CET, when users experienced noticeable slowness while accessing the West Europe \(Production 1\) environment. The issue was detected at 9:28 AM CET…6h 45mResolved
Dec 12, 2025DNS issue on accessing Templafy - All production environments**Investigation** On December 12, 2025, at 09:11 AM CET, a subset of users began experiencing issues when accessing Templafy Hive and Templafy One. The incident was detected at 09:19 AM CET by our internal monitoring…97h 37mResolved
Nov 6, 2025Desktop clients are failing when checking for updates**Investigation** The incident was **first reported at 1:14 AM CET on November 5, 2025**, when a customer noticed that some users experienced failed package updates through Templafy Desktop. The incident was formally…3h 36mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Templafy incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Templafy Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Templafy acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Templafy outage in this window ran 4d 1h, against a mean recovery of 9h 27m. If you depend on Templafy in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.