User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 min ago. Last stored result reached it in 908 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 773 ms | 0 |
| Tue 00 | 0 | 0.0 | 810 ms | 0 |
| Tue 02 | 0 | 0.0 | 869 ms | 0 |
| Tue 04 | 0 | 0.0 | 1143 ms | 0 |
| Tue 06 | 0 | 0.0 | 979 ms | 0 |
| Tue 09 | 0 | 0.0 | 863 ms | 0 |
| Tue 11 | 0 | 0.0 | 676 ms | 0 |
| Tue 13 | 0 | 0.0 | 710 ms | 0 |
| Tue 15 | 0 | 0.0 | 765 ms | 0 |
| Tue 17 | 0 | 0.0 | 883 ms | 0 |
| Tue 20 | 0 | 0.0 | 844 ms | 0 |
| Tue 22 | 0 | 0.0 | 781 ms | 0 |
| Wed 00 | 0 | 0.0 | 1086 ms | 0 |
| Wed 02 | 0 | 0.0 | 1221 ms | 0 |
| Wed 05 | 0 | 0.0 | 863 ms | 0 |
| Wed 07 | 0 | 0.0 | 872 ms | 0 |
| Wed 09 | 0 | 0.0 | 878 ms | 0 |
| Wed 11 | 0 | 0.0 | 852 ms | 0 |
| Wed 14 | 0 | 0.0 | 835 ms | 0 |
| Wed 16 | 0 | 0.0 | 901 ms | 0 |
| Wed 18 | 0 | 0.0 | 765 ms | 0 |
| Wed 20 | 0 | 0.0 | 882 ms | 0 |
| Wed 22 | 0 | 0.0 | 781 ms | 0 |
| Thu 00 | 0 | 0.0 | 753 ms | 0 |
| Thu 03 | 0 | 0.0 | 947 ms | 0 |
| Thu 05 | 0 | 0.0 | 901 ms | 0 |
| Thu 07 | 0 | 0.0 | 952 ms | 0 |
| Thu 09 | 0 | 0.0 | 829 ms | 0 |
| Thu 11 | 0 | 0.0 | 753 ms | 0 |
| Thu 13 | 0 | 0.0 | 968 ms | 0 |
| Thu 15 | 0 | 0.0 | 851 ms | 0 |
| Thu 17 | 0 | 0.0 | 979 ms | 0 |
| Thu 19 | 0 | 0.0 | 801 ms | 0 |
| Thu 21 | 0 | 0.0 | 817 ms | 0 |
| Thu 23 | 0 | 0.0 | 896 ms | 0 |
| Fri 01 | 0 | 0.0 | 848 ms | 0 |
| Fri 03 | 0 | 0.0 | 898 ms | 0 |
| Fri 06 | 0 | 0.0 | 858 ms | 0 |
| Fri 08 | 0 | 0.0 | 751 ms | 0 |
| Fri 10 | 0 | 0.0 | 909 ms | 0 |
| Fri 12 | 0 | 0.0 | 787 ms | 0 |
| Fri 14 | 0 | 0.0 | 824 ms | 0 |
| Fri 16 | 0 | 0.0 | 820 ms | 0 |
| Fri 17 | 0 | 0.0 | 983 ms | 0 |
| Fri 18 | 0 | 0.0 | 981 ms | 0 |
| Fri 19 | 0 | 0.0 | 1119 ms | 0 |
| Fri 21 | 0 | 0.0 | 908 ms | 0 |
| Fri 23 | 0 | 0.0 | 987 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Templafy yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Templafy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Templafy alerts to Slack, Discord or a webhook — free.
We track Templafy (templafy.com) as part of the Productivity group. Agentic enterprise document generation for better consistency, higher quality, and faster document workflows.
Templafy publishes an official status page at status.templafy.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 893 ms average, 741–1119 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Templafy incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
893 ms on average over the last 24 hours (741–1119 ms).
Yes, at https://status.templafy.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Templafy here at once, the problem is on Templafy's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Templafy. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.