TIMIFY Outage History

TIMIFY is up right now

Pingoru has recorded 7 incidents for TIMIFY: 5 in the last 12 months and 3 in the last 90 days.

Source: status.timify.com

7incidents recorded
5last 12 months
3last 90 days
76 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking TIMIFY in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202625 of 744 (1%)
November 202600 of 128 (0%)

Incidents, newest first

Major October 9, 2026 Disruption affecting the Booking Widget and Web App 30m

Started Oct 09, 2026, 09:30 AM UTC· resolved Oct 09, 2026, 10:00 AM UTC

  1. resolved Oct 09, 2026, 12:00 PM UTC

    On 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 working as expected. The service has been restored and we are monitoring it closely. We are working with our database provider to identify the cause and will share an update once we have their findings. We apologise for any inconvenience this may have caused you and your customers.

Read the full incident report →

Major October 5, 2026 Appointment reservations not cleared as expected in some cases 4h Web App, Mobile App, Tablet app

Started Oct 05, 2026, 03:37 PM UTC· resolved Oct 05, 2026, 07:38 PM UTC

  1. investigating Oct 05, 2026, 03:37 PM UTC

    In some cases, reservations of appointment slots are not released or cleared as expected. The affected slots stay blocked and cannot be booked by other customers, which reduces the availability clients offer.

  2. investigating Oct 05, 2026, 04:26 PM UTC

    We are still investigating the annomaly

  3. identified Oct 05, 2026, 06:11 PM UTC

    We have identified the root cause of the issue where appointment reservations were not cleared as expected in some cases and our team is working on a fix.

  4. identified Oct 05, 2026, 06:23 PM UTC

    The fix has been implemented and is being deployed now. We are also cleaning up the affected reservation entries during the day, so the calendars will be free of this data. The booking process itself is not affected We will confirm as soon as the cleanup is completed.

  5. monitoring Oct 05, 2026, 07:26 PM UTC

    The fix has been deployed. New created reservations are working as expected. The cleanup of the affected reservation entries is running as expected, and we are monitoring the functionality. We will confirm as soon as the cleanup is completed.

  6. resolved Oct 05, 2026, 07:38 PM UTC

    The 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 your patience.

Read the full incident report →

Major September 21, 2026 Partial disruption to multiple applications functionalities 22m Web App, Branch Manager, Customer booking process

Started Sep 21, 2026, 11:07 AM UTC· resolved Sep 21, 2026, 11:30 AM UTC

  1. investigating Sep 21, 2026, 11:07 AM UTC

    We are currently investigating an issue affecting different functionalities across multiple applications. We will post updates as more information becomes available.

  2. monitoring Sep 21, 2026, 11:17 AM UTC

    We are observing that functionality is returning to normal across the affected apps. We are continuing to monitor the situation closely and will confirm full resolution shortly.

  3. resolved Sep 21, 2026, 11:30 AM UTC

    This 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.

Read the full incident report →

Notice May 8, 2026 Elevated CPU Usage on Primary Database Cluster 1h

Started May 08, 2026, 11:05 AM UTC· resolved May 08, 2026, 12:05 PM UTC

  1. resolved May 08, 2026, 11:00 AM UTC

    Between 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 resulted in intermittent failures across several system functionalities. Following a configuration adjustment, load balancing has been restored and all systems are operating normally.

Read the full incident report →

Major January 14, 2026 Issue with Branch Manager 24m Branch Manager

Started Jan 14, 2026, 10:10 AM UTC· resolved Jan 14, 2026, 10:35 AM UTC

  1. investigating Jan 14, 2026, 10:10 AM UTC

    We are currently investigating an issue with our Branch Manager web application. This may affect your ability to use the product.

  2. investigating Jan 14, 2026, 10:11 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 14, 2026, 10:29 AM UTC

    We have identified the issue and the affected areas, and have taken measures to improve the situation. We are now monitoring the system closely.

  4. resolved Jan 14, 2026, 10:35 AM UTC

    The incident has been resolved. The system is stable again and we will continue to monitor the situation.

Read the full incident report →

Notice August 26, 2025 Issue with Developer API Endpoints –

Started Aug 26, 2025, 02:00 PM UTC· resolved Aug 26, 2025, 02:00 PM UTC

  1. resolved Aug 26, 2025, 02:00 PM UTC

    Status: Fully Resolved Impact: Developer API, Marketplace Apps (e.g. SSO) Timeframe: 09:18 UTC - 12:35 UTC What Happened: An issue affected several endpoints in the TIMIFY Developer API, causing unexpected behaviour for applications relying on the following endpoints groups: Company, EnterprisesCompanies, Resources, BookerServices. This also impacted certain TIMIFY Marketplace applications that depend on these endpoints - such as SSO login - leading to limited functionality or failed requests. Actions Taken: - The issue was thoroughly analysed and verified in our development and test environments. - A hotfix was successfully deployed to the production environment. - Full functionality has been restored for all users. We sincerely apologize for the inconvenience and any disruption this may have caused to your operations. We are committed to maintaining the reliability of our services and continuously improving our processes to prevent future issues. Thank you for your patience and understanding.

Read the full incident report →

Minor July 15, 2025 Issue with Attribute Configuration in Branch Manager 38m Branch Manager

Started Jul 15, 2025, 02:11 PM UTC· resolved Jul 15, 2025, 02:50 PM UTC

  1. investigating Jul 15, 2025, 02:11 PM UTC

    We are currently investigating an issue with our “Attributes” feature. At the moment, attribute configuration data cannot be listed in the Branch Manager application. This may affect your ability to view or manage custom attributes.

  2. monitoring Jul 15, 2025, 02:29 PM UTC

    Our work on this issue is still ongoing. We have rolled back the change that caused the problem and verified the fix in our development and test environments. If you’re still experiencing issues, please try reloading the page using: - Mac: Command + Shift + R - Windows/Linux: Ctrl + Shift + R We’re closely monitoring the system and will provide further updates shortly. Thank you for your continued patience.

  3. resolved Jul 15, 2025, 02:50 PM UTC

    Current Status & Actions Taken: The issue has now been fully resolved for all users. We first reverted a recent update of our Branch Manager application, which was identified as the root cause. In a second step, we provided a fix that was verified in our development and test environments before restoring normal functionality in production. Scope: Only users actively using the “Attributes” feature in the Branch Manager application were affected. If You’re Still Having Trouble: Please try reloading the application using: - Mac: Command + Shift + R - Windows/Linux: Ctrl + Shift + R We sincerely apologize for any disruption this may have caused. Thank you for your patience while we worked to restore full functionality.

Read the full incident report →