User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
myfitapp.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 1 hr ago. Last stored result reached it in 1931 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1963 ms | 0 |
| Nov 7 | 0 | 0.0 | 1910 ms | 0 |
| Nov 7 | 0 | 0.0 | 2187 ms | 0 |
| Nov 7 | 0 | 0.0 | 2028 ms | 0 |
| Nov 7 | 0 | 0.0 | 2054 ms | 0 |
| Nov 8 | 0 | 0.0 | 1999 ms | 0 |
| Nov 8 | 0 | 0.0 | 2039 ms | 0 |
| Nov 8 | 0 | 0.0 | 2023 ms | 0 |
| Nov 8 | 0 | 0.0 | 2037 ms | 0 |
| Nov 9 | 0 | 0.0 | 2037 ms | 0 |
| Nov 9 | 0 | 0.0 | 2128 ms | 0 |
| Nov 9 | 0 | 0.0 | 2067 ms | 0 |
| Nov 9 | 0 | 0.0 | 2098 ms | 0 |
| Nov 10 | 0 | 0.0 | 2203 ms | 0 |
| Nov 10 | 0 | 0.0 | 2043 ms | 0 |
| Nov 10 | 0 | 0.0 | 1949 ms | 0 |
| Nov 10 | 0 | 0.0 | 2003 ms | 0 |
| Nov 11 | 0 | 0.0 | 2070 ms | 0 |
| Nov 11 | 0 | 0.0 | 1853 ms | 0 |
| Nov 11 | 0 | 0.0 | 2000 ms | 0 |
| Nov 11 | 0 | 0.0 | 2037 ms | 0 |
| Nov 12 | 0 | 0.0 | 1991 ms | 0 |
| Nov 12 | 0 | 0.0 | 1941 ms | 0 |
| Nov 12 | 0 | 0.0 | 2158 ms | 0 |
| Nov 12 | 0 | 0.0 | 1960 ms | 0 |
| Nov 13 | 0 | 0.0 | 1966 ms | 0 |
| Nov 13 | 0 | 0.0 | 2104 ms | 0 |
| Nov 13 | 0 | 0.0 | 1907 ms | 0 |
| Nov 13 | 0 | 0.0 | 1932 ms | 0 |
| Nov 14 | 0 | 0.0 | 1943 ms | 0 |
| Nov 14 | 0 | 0.0 | 1928 ms | 0 |
| Nov 14 | 0 | 0.0 | 1931 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for myFitApp yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when myFitApp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send myFitApp alerts to Slack, Discord or a webhook — free.
myFitApp is listed in our Cloud & developer category and checked at myfitapp.com. A fully customisable app solution to strengthen your brand, retain members, and acquire new ones. Trusted by millions of members, globally.
myFitApp publishes an official status page at status.myfitapp.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 1938 ms average, 1844–2042 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public myFitApp incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1938 ms on average over the last 24 hours (1844–2042 ms).
Yes, at https://status.myfitapp.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report myFitApp here at once, the problem is on myFitApp'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 myFitApp. 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.