User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Fitbit integration retired by Google
Source: the vendor's status page · We are not affiliated with Terra.
Estimated fix: Not enough Terra history yet; similar Health outages lasted 8 min (median, typically 8 min–16 min; 85 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 40 min ago. Last stored result reached it in 109 ms.
Critical incident
Fitbit integration retired by Google Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:15 | 0 | 0.0 | 107 ms | 0 |
| 11:15 | 0 | 0.0 | 253 ms | 0 |
| 13:15 | 0 | 0.0 | 197 ms | 0 |
| 15:30 | 0 | 0.0 | 237 ms | 0 |
| 17:30 | 0 | 0.0 | 134 ms | 0 |
| 19:30 | 0 | 0.0 | 124 ms | 0 |
| 21:45 | 0 | 0.0 | 243 ms | 0 |
| 23:45 | 0 | 0.0 | 317 ms | 0 |
| 01:45 | 0 | 0.0 | 155 ms | 0 |
| 03:45 | 0 | 0.0 | 98 ms | 0 |
| 06:00 | 0 | 0.0 | 231 ms | 0 |
| 08:00 | 0 | 0.0 | 109 ms | 0 |
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.
One report per service every 10 minutes from this network. No account.
Get an email when Terra goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Terra alerts to Slack, Discord or a webhook — free.
Terra, at tryterra.co, is one of the Health services we monitor. The leading health data API for developers. Connect 500+ sources, from wearables and sensors to blood and DNA tests, through one API.
Terra publishes an official status page at status.tryterra.co; when we can read it, its incident level is folded into the status shown here.
Typical issues 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. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 181 ms average, 54–317 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Fitbit integration retired by Google
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 16 h. 1 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
181 ms on average over the last 24 hours (54–317 ms).
Yes, at https://status.tryterra.co.
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 Terra here at once, the problem is on Terra'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 Terra. 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.