Monitoring - we carried out a short maintenance window (5–15 minutes) to upgrade the underlying environment. The machine received additional resources, including increased CPU and memory. We expect this to improve performance, and we will continue to monitor the system closely. Further improvements are still in progress, and we appreciate your patience.
Nov 24, 2025 - 14:27 CET
Identified - We have applied several adjustments and fixes designed to improve the application's performance.
We continue to investigate the underlying root causes and will implement additional application-level and system-level improvements as our analysis progresses.
Nov 21, 2025 - 15:54 CET
Investigating - We are currently investigating a service issue affecting a subset of customers. Since Sunday, some users have experienced performance degradation and brief periods of limited availability.
Our team is actively working to identify the underlying causes and is continuously monitoring system performance to stabilize the service. We will continue dedicated efforts in the coming days to improve overall responsiveness and restore full availability.
We apologize for the inconvenience and appreciate your patience while we work toward a permanent resolution.
Nov 20, 2025 - 11:35 CET
Completed -
The scheduled maintenance has been completed.
Nov 24, 14:24 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 24, 14:00 CET
Scheduled -
We will perform a short maintenance window (5–15 minutes) today between 14:00 and 14:30 to upgrade the underlying environment. This upgrade increases capacity and addresses recent performance issues. During this period, the application may be temporarily unavailable. Thank you for your understanding.
Nov 24, 10:26 CET
Resolved -
Timetracker Cloud was temporarily unavailable to customers. The underlying cause is still under investigation, but service has already been restored and is fully accessible again. We are currently analysing the root cause and closely monitoring system behaviour.
Preliminary evidence suggests that the server experienced an unexpected shutdown and subsequent restart. Although the server itself came back online, the application layer did not recover as expected, resulting in service unavailability. Our monitoring tools detected the infrastructure interruption and successful restart, but did not indicate that the application remained offline.
We sincerely apologise for the disruption. Preventing a recurrence is our priority, and further details will be shared in the upcoming post-mortem.
Nov 16, 20:00 CET