Skip to content

Outage tracker / MyFitnessPal

Is MyFitnessPal down?

I'm having a problem

Vendor reports no incidentWhat MyFitnessPal reports

MyFitnessPal reports no incident on its status page.

As of the last successful poll, 2026-11-07 17:34 UTC.

MyFitnessPal's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 5 minutes ago

Our checks of MyFitnessPal pass from all 4 regions we check.

As of Nov 7, 2026, 5:32 PM UTC, RealUptime's checks of MyFitnessPal passed in all 4 regions that returned a reading.

Front-door checks

Email me when MyFitnessPal reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is MyFitnessPal's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 7, 2026, 5:32 PM UTC
US-East965 msChecks passing
US-West739 msChecks passing
Europe743 msChecks passing
Asia-Pacific1599 msChecks passing
their status pagetheir claim, not our reading

MyFitnessPal reports: All systems operational (“All Systems Operational”)

from MyFitnessPal's own status page, checked Nov 7, 2026, 3:37 PM UTC
MyFitnessPal's own status page shows no incident, and our checks of MyFitnessPal pass right now.

MyFitnessPal's own component breakdown, as they publish it

  • iOS AppOperational
  • Android AppOperational
  • Web AppOperational
  • API PlatformOperational
  • Fitbit IntegrationsOperational

These are MyFitnessPal's components, named and scored by MyFitnessPal. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is MyFitnessPal's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

MyFitnessPal response time, by region

US-East
1.5sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.3s2026-11-06 UTC: p95 2.1s2026-11-07 UTC: p95 1.5s
Oct 9Oct 23Nov 7
US-West
2.7sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 3.2s2026-11-06 UTC: p95 2.1s2026-11-07 UTC: p95 2.7s
Oct 9Oct 23Nov 7
Europe
1.4sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.7s2026-11-06 UTC: p95 1.6s2026-11-07 UTC: p95 1.4s
Oct 9Oct 23Nov 7
Asia-Pacific
1.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.3s2026-11-06 UTC: p95 1.9s2026-11-07 UTC: p95 1.8s
Oct 9Oct 23Nov 7

Check your own site while you wait on MyFitnessPal

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not MyFitnessPal. It cannot diagnose MyFitnessPal's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 965msstatus code: 200checked: Nov 7, 2026, 5:30 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach MyFitnessPal normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 739msstatus code: 200checked: Nov 7, 2026, 5:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach MyFitnessPal normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionMyFitnessPal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionMyFitnessPal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionMyFitnessPal is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 743msstatus code: 200checked: Nov 7, 2026, 5:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach MyFitnessPal normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionMyFitnessPal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1599msstatus code: 200checked: Nov 7, 2026, 5:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach MyFitnessPal normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionMyFitnessPal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionMyFitnessPal is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using MyFitnessPal, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for MyFitnessPal yet, which is not evidence that nothing is wrong.

Recent probe events

MFP Systems Down, 1h 44mdeclared on their status page2026-07-19
Android account creation and login are degraded, 4h 1mdeclared on their status page2026-05-27
New account signup functionality on mobile (iOS/Android) failing, 1h 11mdeclared on their status page2026-01-20
Search functionality degraded, 24h 57mdeclared on their status page2026-01-19
Cloudflare Global Network Incident, 2h 47mdeclared on their status page2025-11-18
Ability to sign-up/sign-in are degraded, 6h 31mdeclared on their status page2025-10-30
Cloud Provider Outage Impacting MFP System, 5h 53mdeclared on their status page2025-10-20
Elevated Errors and Latency, 1h 4mdeclared on their status page2025-06-23

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring MyFitnessPal since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for MyFitnessPal covering any window you pick, with our check readings and MyFitnessPal's own claim at the time, side by side.

Full check history for MyFitnessPal: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

MyFitnessPal uptime by RealUptime's checksLive, from this page's own readings.
[![MyFitnessPal uptime by RealUptime's checks](https://realuptime.io/outages/myfitnesspal/badge.svg?days=30)](https://realuptime.io/outages/myfitnesspal)
<a href="https://realuptime.io/outages/myfitnesspal"><img src="https://realuptime.io/outages/myfitnesspal/badge.svg?days=30" alt="MyFitnessPal uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is MyFitnessPal down?", https://realuptime.io/outages/myfitnesspal. The readings change with every check, so give the date you read them.

What we check

primary
https://www.myfitnesspal.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.myfitnesspal.com

RealUptime is not affiliated with MyFitnessPal; the name identifies what we checked, and nothing here speaks for MyFitnessPal's own team. We send a single web request to MyFitnessPal from 4 regions on our own schedule and time the response. We do not see inside MyFitnessPal's systems, do not use an account or real transaction, and are not the same signal MyFitnessPal's own team has access to. Treat this as one external data point, not a verdict. What we check for MyFitnessPal is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. MyFitnessPal operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (5 of 14 days so far, 2099 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.