Skip to content

Dexcom G6Recalls & reported problems across all models

Dexcom, Inc. · 13 models in the FDA device registry

Data updated Oct 16, 2026 from official FDA records · Editorial policy

5 open recalls name at least one Dexcom G6 model. Check whether yours is affected in the recall details, and contact the manufacturer or your healthcare provider.

Adverse event reports
637,302
Deaths reported
8
Injuries reported
5,207
Recalls
7

We found 13 models of Dexcom G6 by Dexcom, Inc. in the FDA's device registry (GUDID). Together they are named in 637,302 adverse event reports in the FDA's MAUDE database, received between Jun 5, 2017 and Sep 30, 2026 — classified as 8 deaths, 5,207 injuries, 632,087 malfunctions.

The most frequently reported specific device problem is “Wireless Communication Problem” (292,521 reports).

7 FDA recall records name at least one of these models by its device identifier, 5 still open.

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event. Widely used products collect more reports, so totals can't be used to compare products or estimate failure rates. Only reports that name a model's exact device identifier are counted. What reports can and can't tell you · How this data works

Reports received per month, all models

Nov 2023: 7,984 reportsDec 2023: 6,878 reportsJan 2024: 7,592 reportsFeb 2024: 6,346 reportsMar 2024: 4,617 reportsApr 2024: 4,659 reportsMay 2024: 3,339 reportsJun 2024: 3,584 reportsJul 2024: 3,360 reportsAug 2024: 2,720 reportsSep 2024: 3,157 reportsOct 2024: 2,938 reportsNov 2024: 2,094 reportsDec 2024: 1,343 reportsJan 2025: 1,560 reportsFeb 2025: 884 reportsMar 2025: 980 reportsApr 2025: 597 reportsMay 2025: 1,520 reportsJun 2025: 1,907 reportsJul 2025: 2,484 reportsAug 2025: 2,161 reportsSep 2025: 1,395 reportsOct 2025: 1,406 reportsNov 2025: 1,038 reportsDec 2025: 662 reportsJan 2026: 762 reportsFeb 2026: 576 reportsMar 2026: 478 reportsApr 2026: 348 reportsMay 2026: 274 reportsJun 2026: 261 reportsJul 2026: 178 reportsAug 2026: 104 reportsSep 2026: 127 reportsOct 2026: 0 reports2024202520267,984
Last 36 months. The most recent month may be incomplete.

Dexcom G6 recalls

FDA recall records that name at least one of these models by its device identifier, newest first. Each recall usually covers specific models or lots, so check the details.

  1. Aug 28, 2025Open, Classified

    A software defect in version v1.15.0 of the G6 Android app can cause the app to terminate unexpectedly, which may result in the user not receiving estimated glucose values, alarms, alerts or notifications. This could result in the missed detection of a hyperglycemic or hypoglycemic event, protentional resulting in severe hyperglycemia, diabetic ketoacidosis (DKA), or hyperosmolar hyperglycemic state (HHS).

    Z-0318-2026 · Root cause: Software Design Change · Recall details · FDA record ↗

  2. May 12, 2025Open, Classified

    Defective foam or an assembly error may cause the receiver speaker to lose contact with the printed circuit board, leading to missed audible alerts for low or high blood glucose values. A missed audible alert for low or high blood glucose values could lead to untreated hypo or hyperglycemia which can cause seizures, vomiting, loss of consciousness, or death.

    Z-1943-2025 · Root cause: Nonconforming Material/Component · names 2 of these models · Recall details · FDA record ↗

  3. Jan 27, 2025Open, Classified

    Under very rare situations, the Dexcom G6 touchscreen receiver may not provide high or low glucose alarms/alerts as designed, which can result in two different conditions. First, if a receiver operating system .net error occurs when an alarm/alert should be triggered, the initial alarm/alert will not be delivered until a subsequent alarm/alert is triggered. At that time, the initial alarm/alert is delivered, but not the second one. Alarm/alerts will continue to be delayed and be one alarm/alert behind, causing delayed alarm/alerts until the receiver is reset. This condition could result in the missed detection of a hyperglycemic or hypoglycemic event. Second, a single EGV reading may be delayed for 5 minutes after the initial .net operating system error. If the user receives a single EGV reading delayed by 5 minutes, the delay is not expected to cause user harm.

    Z-1204-2025 · Root cause: Software design · Recall details · FDA record ↗

  4. Jan 27, 2025Open, Classified

    Under very rare situations, the Dexcom G6 touchscreen receiver may not provide high or low glucose alarms/alerts as designed, which can result in two different conditions. First, if a receiver operating system .net error occurs when an alarm/alert should be triggered, the initial alarm/alert will not be delivered until a subsequent alarm/alert is triggered. At that time, the initial alarm/alert is delivered, but not the second one. Alarm/alerts will continue to be delayed and be one alarm/alert behind, causing delayed alarm/alerts until the receiver is reset. This condition could result in the missed detection of a hyperglycemic or hypoglycemic event. Second, a single EGV reading may be delayed for 5 minutes after the initial .net operating system error. If the user receives a single EGV reading delayed by 5 minutes, the delay is not expected to cause user harm.

    Z-1203-2025 · Root cause: Software design · Recall details · FDA record ↗

  5. Jan 27, 2025Open, Classified

    Under very rare situations, the Dexcom G6 touchscreen receiver may not provide high or low glucose alarms/alerts as designed, which can result in two different conditions. First, if a receiver operating system .net error occurs when an alarm/alert should be triggered, the initial alarm/alert will not be delivered until a subsequent alarm/alert is triggered. At that time, the initial alarm/alert is delivered, but not the second one. Alarm/alerts will continue to be delayed and be one alarm/alert behind, causing delayed alarm/alerts until the receiver is reset. This condition could result in the missed detection of a hyperglycemic or hypoglycemic event. Second, a single EGV reading may be delayed for 5 minutes after the initial .net operating system error. If the user receives a single EGV reading delayed by 5 minutes, the delay is not expected to cause user harm.

    Z-1202-2025 · Root cause: Software design · Recall details · FDA record ↗

  6. Feb 3, 2020Terminated

    The company identified potential interference from hydroxyurea. Patient use of the anti-neoplastic drug may falsely elevate glucose readings on the Continuous Glucose Monitoring Systems.

    Z-1562-2020 · Root cause: Under Investigation by firm · Recall details · FDA record ↗

  7. Nov 19, 2019Terminated

    It was reported that the user's low alarm feature on the iOS application were not properly alerting users when the user has enabled the Alert Schedule feature more than 30 days after installing the iOS application.

    Z-1104-2020 · Root cause: Software design · Recall details · FDA record ↗

Most reported Dexcom G6 problems

Device problems

  • Wireless Communication Problem292,521
  • No Device Output180,230
  • Imprecision42,021
  • Premature End-of-Life Indicator34,477
  • Incorrect, Inadequate or Imprecise Result or Readings19,327
  • Detachment of Device or Device Component10,340
  • Appropriate Device Problem Term/Code Not Available10,228
  • Unintended Application Program Shut Down6,310

Patient problems

  • No Clinical Signs, Symptoms or Conditions383,475
  • No Consequences Or Impact To Patient221,902
  • Hyperglycemia27,310
  • Hypoglycemia5,593
  • Loss of consciousness1,263
  • Foreign Body In Patient1,097
  • Dizziness802
  • Fatigue651

Dexcom G6 models

13 models, most reported first. Each model has its own page with its reports, recalls and device details.

Recent Dexcom G6 adverse event reports

The 15 most recent reports across all models, in the reporter's own words as published by the FDA.

Other Dexcom, Inc. products

All Dexcom, Inc. devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page