Skip to content
DeutschSign in

Is Fitbit down right now?

fitbit.com

Checking fitbit.com…

Asking our locations to reach the site. This takes a few seconds.

Uptime, 24 hours
100 %
Uptime, 7 days
100 %
Uptime, 30 days
100 %

Based on 1 day of checks so far. Checks that failed because of how we test, not because of the site, are left out.

Response time, last 24 hours

2026-10-09 11:03 UTC: 637 ms2026-10-09 11:19 UTC: 688 ms2026-10-09 11:34 UTC: 606 ms2026-10-09 11:50 UTC: 635 ms2026-10-09 12:06 UTC: 651 ms2026-10-09 12:21 UTC: 731 ms2026-10-09 12:37 UTC: 795 ms2026-10-09 12:52 UTC: 735 ms2026-10-09 13:08 UTC: 660 ms2026-10-09 13:24 UTC: 712 ms2026-10-09 13:40 UTC: 682 ms2026-10-09 13:55 UTC: 596 ms2026-10-09 14:11 UTC: 718 ms2026-10-09 14:26 UTC: 670 ms2026-10-09 14:42 UTC: 661 ms2026-10-09 14:57 UTC: 595 ms2026-10-09 15:13 UTC: 616 ms2026-10-09 15:29 UTC: 682 ms2026-10-09 15:44 UTC: 570 ms2026-10-09 16:00 UTC: 616 ms2026-10-09 16:15 UTC: 764 ms2026-10-09 16:31 UTC: 675 ms
Green: response time, full height at 1100 ms or more. Red: down. Amber: not confirmed.

Response time by location, last 24 hours

LocationAverage responseReached
Berlin 1, Germany661 ms22 of 22 checks
Falkenstein, Germany666 ms22 of 22 checks
Berlin 2, Germany674 ms22 of 22 checks

Each check runs from all locations at once. A location far from the site’s servers answers later; that says nothing about the site being slow.

Outage history

No confirmed outage on record. An outage is listed once Fitbit could not be reached from at least two locations in two checks in a row.

Recent checks

TimeStatusLocationsResponse
2026-10-09 16:31 UTCUp3 of 3675 ms
2026-10-09 16:15 UTCUp3 of 3764 ms
2026-10-09 16:00 UTCUp3 of 3616 ms
2026-10-09 15:44 UTCUp3 of 3570 ms
2026-10-09 15:29 UTCUp3 of 3682 ms
2026-10-09 15:13 UTCUp3 of 3616 ms
2026-10-09 14:57 UTCUp3 of 3595 ms
2026-10-09 14:42 UTCUp3 of 3661 ms

Comments

0/500 · no links · do not post personal data

No comments yet. Be the first to say what you are seeing.

We can reach it, but you cannot?
  • Reload the page without the cache: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  • Open the site in a private window. If it works there, clear the cookies and cache for fitbit.com.
  • Try another network, such as mobile data. If that works, the problem is with your provider or router.
  • Switch to a public DNS resolver such as 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
  • Turn off VPNs, proxies and ad blockers for a moment. Some sites refuse those connections.
Embed a status badge

Show the current status of Fitbit on your own page or in a README. The badge updates by itself.

Status of fitbit.com

Similar sites