User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
Is Fit3D down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → fit3d.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 57 min ago. Last stored result reached it in 72 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 56 ms | 0 |
| Tue 01 | 0 | 0.0 | 113 ms | 0 |
| Tue 03 | 0 | 0.0 | 209 ms | 0 |
| Tue 05 | 0 | 0.0 | 64 ms | 0 |
| Tue 07 | 0 | 0.0 | 75 ms | 0 |
| Tue 09 | 0 | 0.0 | 95 ms | 0 |
| Tue 11 | 0 | 0.0 | 57 ms | 0 |
| Tue 13 | 0 | 0.0 | 115 ms | 0 |
| Tue 16 | 0 | 0.0 | 76 ms | 0 |
| Tue 18 | 0 | 0.0 | 77 ms | 0 |
| Tue 20 | 0 | 0.0 | 66 ms | 0 |
| Tue 22 | 0 | 0.0 | 62 ms | 0 |
| Wed 01 | 0 | 0.0 | 139 ms | 0 |
| Wed 03 | 0 | 0.0 | 90 ms | 0 |
| Wed 05 | 0 | 0.0 | 38 ms | 0 |
| Wed 07 | 0 | 0.0 | 97 ms | 0 |
| Wed 10 | 0 | 0.0 | 68 ms | 0 |
| Wed 12 | 0 | 0.0 | 54 ms | 0 |
| Wed 14 | 0 | 0.0 | 62 ms | 0 |
| Wed 16 | 0 | 0.0 | 86 ms | 0 |
| Wed 18 | 0 | 0.0 | 42 ms | 0 |
| Wed 20 | 0 | 0.0 | 78 ms | 0 |
| Wed 23 | 0 | 0.0 | 94 ms | 0 |
| Thu 01 | 0 | 0.0 | 83 ms | 0 |
| Thu 03 | 0 | 0.0 | 80 ms | 0 |
| Thu 05 | 0 | 0.0 | 80 ms | 0 |
| Thu 07 | 0 | 0.0 | 41 ms | 0 |
| Thu 09 | 0 | 0.0 | 89 ms | 0 |
| Thu 11 | 0 | 0.0 | 46 ms | 0 |
| Thu 13 | 0 | 0.0 | 93 ms | 0 |
| Thu 15 | 0 | 0.0 | 84 ms | 0 |
| Thu 17 | 0 | 0.0 | 81 ms | 0 |
| Thu 19 | 0 | 0.0 | 93 ms | 0 |
| Thu 21 | 0 | 0.0 | 134 ms | 0 |
| Thu 23 | 0 | 0.0 | 57 ms | 0 |
| Fri 02 | 0 | 0.0 | 74 ms | 0 |
| Fri 04 | 0 | 0.0 | 57 ms | 0 |
| Fri 06 | 0 | 0.0 | 70 ms | 0 |
| Fri 08 | 0 | 0.0 | 33 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 13 | 0 | 0.0 | 58 ms | 0 |
| Fri 15 | 0 | 0.0 | 73 ms | 0 |
| Fri 17 | 0 | 0.0 | 63 ms | 0 |
| Fri 19 | 0 | 0.0 | 108 ms | 0 |
| Fri 20 | 0 | 0.0 | 92 ms | 0 |
| Fri 22 | 0 | 0.0 | 62 ms | 0 |
| Sat 00 | 0 | 0.0 | 72 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Fit3D badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Fit3D yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fit3D?
One report per service every 10 minutes from this network. No account.
Follow Fit3D
Get an email when Fit3D goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fit3D alerts to Slack, Discord or a webhook — free.
About Fit3D
We track Fit3D (fit3d.com) as part of the Health group. Discover Fit3D's 3D body scanning technology for accurate measurements, fitness tracking, and health assessments. Ideal for fitness professionals and enthusiasts.
Fit3D publishes an official status page at status.fit3d.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 69 ms average, 24–108 ms range across 14 successful checks.
Questions
Is Fit3D down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Fit3D last down?
We have not recorded a public Fit3D incident since monitoring began 8 days ago.
What is Fit3D's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Fit3D respond?
69 ms on average over the last 24 hours (24–108 ms).
Does Fit3D have an official status page?
Yes, at https://status.fit3d.com.
Fit3D not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Fit3D here at once, the problem is on Fit3D's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Fit3D. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.