Templafy Outage History

Templafy is up right now

Templafy had 31 outages in the last 2 years totaling 10h 55m of downtime — averaging 1.3 incidents per month.

There were 31 Templafy outages since June 12, 2025 totaling 10h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.templafy.com

Major June 12, 2025

Service degradation - Unable to Save and Share created documents

Detected by Pingoru
Jun 12, 2025, 08:48 AM UTC
Resolved
Jun 12, 2025, 10:18 AM UTC
Duration
1h 29m
Affected: Integrations
Timeline · 5 updates
  1. investigating Jun 12, 2025, 08:48 AM UTC

    We are currently investigating this issue.

  2. identified Jun 12, 2025, 09:00 AM UTC

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

  3. monitoring Jun 12, 2025, 10:14 AM UTC

    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.

  4. resolved Jun 12, 2025, 10:18 AM UTC

    The incident has been resolved, and further information will be provided in a postmortem shortly. We apologize for the impact to affected customers.

  5. postmortem Jun 16, 2025, 07:30 AM UTC

    **Incident Initiation** At 10:18 AM CET on June 12, 2025, we identified an issue that was preventing users from saving and sharing documents through the Library task-pane in both Office on-premises and online environments. **Investigation** Our investigation revealed that the issue stemmed from a change made in the Integration Management system. This update, intended to fix a separate issue in the Composer component, inadvertently impacted the Library task-pane. This change was rolled out by 08:09 AM on June 11, 2025 to all production clusters. **Mitigation and Resolution** To fix the issue, we adjusted the update to ensure it only applied to its intended target. The corrected version was tested and successfully deployed to all production environments at 12:13 PM CET on June 12, 2025. **Impact and Scope** Although the issue was reported by only one tenant, it had the potential to affect all users across all environments, making the impact significant. The issue has been fully resolved.

Read the full incident report →