ClockShark incident

Upstream Dedendency Degredation

Minor Resolved View vendor source →

ClockShark experienced a minor incident on October 20, 2025 affecting app.clockshark.com and Clockshark Time Tracking, lasting 2h 31m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:30 PM UTC
Resolved
Oct 21, 2025, 12:02 AM UTC
Duration
2h 31m
Detected by Pingoru
Oct 20, 2025, 09:30 PM UTC

Affected components

app.clockshark.comClockshark Time Tracking

Update timeline

  1. identified Oct 20, 2025, 09:30 PM UTC

    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.

  2. monitoring Oct 20, 2025, 10:06 PM UTC

    We have deployed an update to bypass the upstream issues. We will continue to monitor.

  3. resolved Oct 21, 2025, 12:02 AM UTC

    All services are functioning normally.