Is Clockify Down?

No — Clockify is up

Reachable from all 8 checked regions

Average response time: 923ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.clockify.me

Clockify uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

762ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

14-day clean streak

Sep 7 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

73ms

DNS 39ms TCP 2ms TLS 5ms TTFB 66ms

arn

138ms

DNS 65ms TCP 3ms TLS 6ms TTFB 106ms

nrt

1680ms

DNS 223ms TCP 2ms TLS 4ms TTFB 961ms

ord

973ms

DNS 372ms TCP 1ms TLS 4ms TTFB 780ms

sin

1051ms

DNS 73ms TCP 1ms TLS 5ms TTFB 572ms

sjc

1064ms

DNS 90ms TCP 1ms TLS 4ms TTFB 562ms

syd

1923ms

DNS 126ms TCP 1ms TLS 6ms TTFB 1033ms

yyz

484ms

DNS 61ms TCP 8ms TLS 13ms TTFB 298ms

What Clockify does

Clockify is time tracking software used by freelancers, agencies and companies to log hours against projects and clients, fill in timesheets and produce the reports that billing and payroll run on. Many teams also use its screenshots and GPS location features to verify hours, so it is often the record that decides what gets invoiced or paid.

What an outage looks like

The web app does not load or timers will not start or stop. Time entries disappear from the list after saving, or save twice. Reports hang or export empty. Imports of time data from files fail. Webhooks to connected tools stop firing, so invoicing and payroll integrations miss entries. Screenshots and location data stop recording for tracked devices.

What to do about it

Check status.clockify.me, which lists the Web App, API, Reporting, File Import, Screenshots, Locations, Webhooks and Calendar as separate services. Write down start and stop times by hand while the timer is unavailable and add them later. Do not rerun report exports or invoices for the incident window until Reporting and Webhooks are healthy.

Is it down for everyone, or just you?

If this page says Clockify is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Clockify outage FAQ

Will I lose the time I tracked during a Clockify outage?

A timer that started before the incident may not have saved its stop time, so check your entries after recovery. Anything you could not start at all needs to be added manually. Keeping a plain note of start and stop times during the incident is the fastest way to fill the gap accurately.

Why are my Clockify reports wrong or empty?

Reporting is a separate service from the Web App, so reports can fail while tracking works. Wait until it recovers before exporting anything used for billing or payroll. Reports run during the incident may be missing recent entries, and invoices built from them would undercount hours.

Did my integrations receive the time entries?

Maybe not. Webhooks is its own service on the status page, and an incident there means connected invoicing, payroll or project tools may have missed entries. After recovery, compare totals in Clockify against the connected tool for the incident window rather than assuming they match.

Is it Clockify or my browser extension?

Try the web app directly. If the web app works and the extension does not, the problem is on your side: reload or sign in to the extension again. If the web app fails too and the Web App row on the status page is degraded, it is Clockify.

Does the Clockify API work when the app is down?

They are reported separately, so check the API row. Scripts and third-party tools that read or write time entries through the API may fail during an incident even if the web app loads, or the other way round. Pause automated imports until both are healthy to avoid partial or duplicated entries.

How we measure this

We request Clockify's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Clockify publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Clockify goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required