ClockShark had 6 outages in the last 2 years totaling 49h 2m of downtime — averaging 0.2 incidents per month.
There were 6 ClockShark outages since September 25, 2025 totaling 49h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified an issue that is affecting access to the top Nav bar in the web application. We are reverting a change that is causing the issue.
Resolved
Clockshark is investigating issues with the web app. All customers are affected.
We have identified the issue and are working on a fix
We’ve applied the change, and will continue to monitor
A configuration change was implemented and tested in lower environments without problems. However, applying the same change in our production environment caused the services to fail to start properly. We promptly reverted the change, restoring the systems to normal operation.
Clockshark is investigating issues with one of our hosting services.One of our dependencies is critically affected by the on-going Cloudflare outage. (https://cloudflarestatus.com). This issue is impacting all services that rely on our core infrastructure, including our web & mobile apps.
Cloudflare is continuing to work on restoring services.
Cloudflare is continuing to work on restoring services
Cloudflare is still working to restore services.
Cloudflare has deployed a fix. We are monitoring to ensure that all of our applications are working.
All services restored.
Clockshark is investigating issues with our hosting services. One of our dependencies is critcally affected by the on-going AWS outage. (https://health.aws.amazon.com/health/status, https://status.launchdarkly.com/) We are creating a bypass of this dependency, will deploy a fix soon. This issue is impacting all services that rely on our core infrastructure, including our web & mobile apps.
We have deployed an update to bypass the upstream issues. We will continue to monitor.
All services are functioning normally.
We’ve identified an issue affecting the latest release of the ClockShark app when running on iOS 26. As a precaution, we have temporarily unpublished the app from the Apple app store while the engineering team works on a fix. Existing users will continue to have the app function normally if they are not on iOS 26 and have not updated to the latest version. They will not auto-update, so they should not see an impact. New iOS users will not be able to download the app until a fix is released to the store. Android users are not impacted by this issue and remain fully functional. We are actively working on a solution and hope to fully restore the app ASAP.
We’ve identified an issue with a specific dependency. We’re reverting that dependency and testing the fix.
The reversion of the dependency fixed the issue. We are submitting the updated ClockShark app to the App Store for review.
The updated application is available in the Apple App Store.
Clockshark is investigating issues with the ADP Integration. Customers using the ADP Integration may be impacted as requests might fail and/or errors may be displayed.
We have identified the issue and are working on a resolution.
We have deployed a fix for the issue and are monitoring to ensure resolution.
The issue has been successfully remediated.