TIMIFY Outage History
5 incidents recorded over the last 365 days, 5 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.
Every Recorded TIMIFY Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 9, 2026 | Disruption affecting the Booking Widget and Web AppOn 09.10.2026 between 11:30 and 12:00 CEST, a database node in our infrastructure restarted unexpectedly. During this time, some functionalities of the Web App and the Booking Widget (Customer booking process) were not… | 0 min | Resolved |
| Oct 5, 2026 | Appointment reservations not cleared as expected in some casesThe cleanup is complete and all affected reservation entries have been removed from the calendars. We have confirmed that everything works as expected. The booking process was not affected at any point. Thank you for… | 4h 0m | Resolved |
| Sep 21, 2026 | Partial disruption to multiple applications functionalitiesThis incident has been resolved. All affected functionalities are back to normal, and the customer booking process is fully operational. Thank you for your patience while we worked through this. | 22 min | Resolved |
| May 8, 2026 | Elevated CPU Usage on Primary Database ClusterBetween 11:05 and 12:05, we experienced elevated CPU spikes on one of our primary database clusters. The root cause was uneven load distribution across the cluster nodes, contrary to the expected configuration. This… | -94 min | Resolved |
| Jan 14, 2026 | Issue with Branch ManagerThe incident has been resolved. The system is stable again and we will continue to monitor the situation. | 24 min | Resolved |
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 TIMIFY 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 TIMIFY 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 TIMIFY 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 TIMIFY outage in this window ran 4h, against a mean recovery of 1h 12m. If you depend on TIMIFY 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.