Is Toggl Track Down?

No — Toggl Track is up

Reachable from all 8 checked regions

Average response time: 638ms

Last checked 53 minutes ago · checks run every 6 hours

Official status page: https://status.toggl.com

Toggl Track uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

510ms

Avg response, 30 days

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

30-day history

68-day clean streak

Sep 14 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.

gru

630ms

DNS 265ms TCP 3ms TLS 9ms TTFB 423ms

iad

230ms

DNS 94ms TCP 2ms TLS 6ms TTFB 136ms

jnb

1610ms

DNS 430ms TCP 2ms TLS 6ms TTFB 680ms

lax

187ms

DNS 113ms TCP 1ms TLS 9ms TTFB 177ms

lhr

202ms

DNS 65ms TCP 3ms TLS 11ms TTFB 182ms

nrt

730ms

DNS 7ms TCP 1ms TLS 5ms TTFB 155ms

ord

261ms

DNS 46ms TCP 20ms TLS 32ms TTFB 147ms

sin

1258ms

DNS 147ms TCP 1ms TLS 6ms TTFB 385ms

What Toggl Track does

Toggl Track is a time tracking tool used by freelancers, agencies and consultancies to log billable hours against clients and projects, from a browser, desktop and mobile apps and a browser extension. The wider Toggl suite adds Plan for scheduling, Work and Focus, and integrations push tracked time into project management and invoicing tools.

What an outage looks like

The web app loads without your time entries, or a running timer will not stop and save. Entries created in the desktop and mobile apps fail to sync, so the same block of time appears on one device and not another. Reports render empty or omit recent days. Integrations stop pushing entries into connected tools, and API calls and webhooks return errors.

What to do about it

Check status.toggl.com, which reports Track separately from the wider Toggl suite and breaks Track into the web app, API, Reports, Integrations and Webhooks, so a reporting-only or integration-only problem is visible rather than guessed at. Note what you were tracking before retrying anything, and reconcile entries against the server once the page is green rather than re-creating them, since duplicates distort billable totals.

Is it down for everyone, or just you?

If this page says Toggl Track 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

Toggl Track outage FAQ

Is Toggl down or is it just my browser?

Check status.toggl.com first, because Toggl reports the web app and the API as separate components, and an incident confined to the API can leave the interface loading while your saves quietly fail. If the page is green, sign in from a private window to rule out a stale session or an extension conflict, then compare with a colleague on the same workspace before assuming a platform outage.

Will I lose time I tracked during an outage?

Entries that saved successfully are stored on the server and are unaffected, while ones that errored may never have committed at all. Before re-entering anything, reload and check what is genuinely recorded, because duplicate entries flow directly into client invoices and take more work to remove than a missing block takes to add back from memory.

Do Toggl integrations catch up after an incident?

Integrations and Webhooks are their own components, so time can be tracked correctly while nothing reaches your project management or invoicing tool. Do not assume the downstream system will backfill on its own. Once the components are operational again, compare a recent date range on both sides and push anything missing rather than trusting that the gap closed itself.

Does a Toggl Track outage affect Toggl Plan?

Not necessarily. The status page separates Track from the Suite, which covers the public website, Accounts, Focus, Work and Plan, so scheduling can be healthy while time tracking is degraded. Accounts is shared between them, though, so an incident there can block sign-in to everything at once even when the individual products are otherwise operational.

How we measure this

We request Toggl Track'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 Toggl Track 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 Toggl Track 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