Is MyFitnessPal Down?

No — MyFitnessPal is up

Reachable from all 8 checked regions

Average response time: 1747ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.myfitnesspal.com

MyFitnessPal uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1412ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 68 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

68-day clean streak

Sep 15 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

lax

1050ms

DNS 220ms TCP 1ms TLS 14ms TTFB 1050ms

lhr

1223ms

DNS 87ms TCP 2ms TLS 13ms TTFB 1223ms

nrt

1856ms

DNS 489ms TCP 0ms TLS 13ms TTFB 1856ms

ord

958ms

DNS 84ms TCP 2ms TLS 12ms TTFB 958ms

sin

2315ms

DNS 321ms TCP 1ms TLS 11ms TTFB 2315ms

sjc

2191ms

DNS 352ms TCP 1ms TLS 21ms TTFB 2191ms

syd

2193ms

DNS 400ms TCP 1ms TLS 13ms TTFB 2192ms

yyz

2190ms

DNS 183ms TCP 1ms TLS 12ms TTFB 2189ms

What MyFitnessPal does

MyFitnessPal is a calorie and nutrition tracking app with a large food database, used to log meals, exercise and weight against a daily target. It runs on iOS, Android and the web, syncs across devices, and connects to fitness trackers and other health apps so that activity recorded elsewhere adjusts the day's calorie budget.

What an outage looks like

The app opens on a spinner or shows yesterday's diary, and food you log does not appear on your other devices. Barcode scanning and food searches return nothing, because the database lookup is a server call rather than anything stored locally. Exercise imported from a connected tracker stops adjusting your calorie goal, and the web version can fail while the phone apps work, or the reverse.

What to do about it

Check status.myfitnesspal.com, which reports the iOS app, Android app, web app, the API platform and Fitbit integrations as five separate components, so a phone-only or integration-only problem is visible rather than guessed at. If one platform is affected, log the day's meals on another. Hold off on signing out or reinstalling while an incident is open, since neither step is reversible.

Is it down for everyone, or just you?

If this page says MyFitnessPal is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

MyFitnessPal outage FAQ

Is MyFitnessPal down or is it my phone?

Check status.myfitnesspal.com, which lists the iOS and Android apps as components separate from the web app. If your platform shows green, open the web version in a browser: if that works, the problem is local to the phone, and fully closing the app or checking for an update usually clears it. If both fail, it is server-side and waiting is the only real fix.

Will I lose the meals I logged during an outage?

Entries that synced are stored on your account and will appear on any device. Ones logged while the app could not reach the server may never have committed. When the service returns, open the diary on the web and compare it against what you remember logging before re-entering anything, because duplicated meals distort the day's totals just as much as missing ones do.

Does a MyFitnessPal outage stop my Fitbit steps syncing?

It can. Fitbit integrations are a separate component on the status page, so activity can stop flowing in while the diary itself works normally. Your steps are still recorded in the Fitbit app regardless of what MyFitnessPal is doing. Once the component recovers the two usually reconcile, but check the affected days rather than assuming the calorie adjustment backfilled on its own.

Why can't I search for foods or scan barcodes?

Because both are server-side lookups against MyFitnessPal's food database rather than anything held on your phone. When the API platform is degraded, search returns nothing and the barcode scanner fails to match, even though the app opens normally and your existing diary is visible. That combination, a working app with a dead search, points at the API platform component rather than at your connection.

How we measure this

We request MyFitnessPal's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where MyFitnessPal publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when MyFitnessPal goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required