MyFitnessPal incident

Inaccurate Barcode Food Data

Critical Resolved View vendor source →

MyFitnessPal experienced a critical incident on March 20, 2024 affecting iOS App and Android App and 1 more component, lasting 4d 22h. The incident has been resolved; the full update timeline is below.

Started
Mar 20, 2024, 03:57 PM UTC
Resolved
Mar 25, 2024, 02:32 PM UTC
Duration
4d 22h
Detected by Pingoru
Mar 20, 2024, 03:57 PM UTC

Affected components

iOS AppAndroid AppWeb App

Update timeline

  1. identified Mar 20, 2024, 03:57 PM UTC

    A subset of food data associated with barcodes has been identified as having inaccurate food brand and name associated with the items. The team is currently working through a data remediation solution.

  2. monitoring Mar 22, 2024, 08:39 PM UTC

    A fix has been implemented to correct the inaccurate food data when logging foods individually to the diary. Degraded performance of the affected foods is still expected in the recipes feature as data cleanup continues.

  3. resolved Mar 25, 2024, 02:32 PM UTC

    Food nutrient and barcode data has been corrected and recipe functionality has been restored.