Skip to content

Outage tracker / MyFitnessPal / In the US

Is MyFitnessPal down in the US?

Vendor reports no incidentWhat MyFitnessPal reports

MyFitnessPal reports no incident on its status page.

As of the last successful poll, 2026-11-07 18:13 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 passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked MyFitnessPal at Nov 7, 2026, 6:19 PM UTC.

Over the last 24 hours we completed 262 checks from Ashburn and San Jose and 262 answered cleanly, 100.00% availability.

Of the 2 other regions we check MyFitnessPal from, all 2 read checks passing right now.

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.

What our Ashburn and San Jose probes measured

AshburnChecks passing140 checks in 24h, 100.00%
San JoseChecks passing122 checks in 24h, 100.00%

Last checked Nov 7, 2026, 6:19 PM UTC.

MyFitnessPal from Ashburn and San Jose over the last 30 days

Over the last 30 days, MyFitnessPal answered our Ashburn probe in 944 ms on average, and 1 check in 20 took longer than 1,605 ms.

Over the last 30 days, MyFitnessPal answered our San Jose probe in 1,298 ms on average, and 1 check in 20 took longer than 2,266 ms.

Ranked by average response time across the 4 cities we check MyFitnessPal from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 911 ms and Tokyo slowest at 1,504 ms.

From Ashburn and San Jose we ran 1,291 checks of MyFitnessPal in 6 days, and 1,290 answered cleanly: 99.92% availability.

1 of the 6 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.58% across 243 checks.

In Ashburn local time (EST), MyFitnessPal was slowest around 12 AM, at 1,202 ms on average over the last 14 days, and quickest around 8 PM, at 760 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7202100.00%1,264 ms
Fri, Nov 6250100.00%1,089 ms
Thu, Nov 5247100.00%1,094 ms
Wed, Nov 4247100.00%945 ms
Tue, Nov 324399.58%1,011 ms
Mon, Nov 2102100.00%1,385 ms

MyFitnessPal outages measured from the US

Our Ashburn and San Jose probes measured no confirmed MyFitnessPal outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check MyFitnessPal from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 115 checks
TokyoChecks passing100.00% of 67 checks

Other countries we check MyFitnessPal from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against MyFitnessPal's public endpoints. They are not user reports, and they are not MyFitnessPal's own status page.

See MyFitnessPal's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but MyFitnessPal has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter