Skip to content

Dexcom G7Recalls & reported problems across all models

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

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

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

Adverse event reports
325,909
Deaths reported
9
Injuries reported
4,307
Recalls
8

We found 32 models of Dexcom G7 by Dexcom, Inc. in the FDA's device registry (GUDID). Together they are named in 325,909 adverse event reports in the FDA's MAUDE database, received between Dec 27, 2022 and Sep 30, 2026 — classified as 9 deaths, 4,307 injuries, 321,576 malfunctions.

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

8 FDA recall records name at least one of these models by its device identifier, 8 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: 2,726 reportsDec 2023: 2,774 reportsJan 2024: 3,807 reportsFeb 2024: 3,368 reportsMar 2024: 3,376 reportsApr 2024: 4,093 reportsMay 2024: 4,520 reportsJun 2024: 4,930 reportsJul 2024: 4,474 reportsAug 2024: 4,796 reportsSep 2024: 5,268 reportsOct 2024: 5,319 reportsNov 2024: 4,884 reportsDec 2024: 2,548 reportsJan 2025: 3,217 reportsFeb 2025: 1,325 reportsMar 2025: 2,041 reportsApr 2025: 1,734 reportsMay 2025: 16,548 reportsJun 2025: 21,924 reportsJul 2025: 25,050 reportsAug 2025: 23,862 reportsSep 2025: 14,777 reportsOct 2025: 11,669 reportsNov 2025: 10,876 reportsDec 2025: 12,714 reportsJan 2026: 67,001 reportsFeb 2026: 10,502 reportsMar 2026: 11,553 reportsApr 2026: 7,665 reportsMay 2026: 4,819 reportsJun 2026: 3,715 reportsJul 2026: 2,985 reportsAug 2026: 3,270 reportsSep 2026: 4,492 reportsOct 2026: 0 reports20242025202667,001
Last 36 months. The most recent month may be incomplete.

Dexcom G7 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. May 27, 2026Open, Classified

    Certain lots of Dexcom G7 sensors originally designated as scrap and intended for destruction were stolen during the destruction process. The sensors were later sold to pharmacies and distributors by Pharmsource, LLC. Lot 1725204004 were designated for destruction because the G7 sensors were not properly sterilized and have an increased risk of skin infection if used. Lot 1725069002 were designated for destruction due to an increased risk of having no sensor readings available or experiencing sensor inaccuracy that includes the potential for missed detection of a hyperglycemic event or incorrect treatment decisions that can result in patient injury, including medical intervention to prevent permanent injury or impairment. Additionally, due to the unknown storage and handling and storage conditions these sensors may have undergone during the distribution, these sensors may present additional risk.

    Z-2574-2026 · Root cause: Nonconforming Material/Component · Recall details · FDA record ↗

  2. Apr 14, 2026Open, Classified

    A software defect in which a low-priority file I/O check blocks the higher-priority thread responsible for processing estimated glucose values (EGVs) and trend arrows. When the app is running in the background, EGV notifications may queue up and then "replay" sequentially when the user brings the app to the foreground, causing the Glucose Compass to flicker through previous EGVs. In more severe instances, the app may perceive signal loss and deploy signal loss mitigations. This delay in EGV and alert processing creates a risk that users may miss detection of a hypoglycemic or hyperglycemic event, or make treatment decisions based on outdated glucose information.

    Z-2164-2026 · Root cause: Software design · Recall details · FDA record ↗

  3. Apr 14, 2026Open, Classified

    A software defect in which a low-priority file I/O check blocks the higher-priority thread responsible for processing estimated glucose values (EGVs) and trend arrows. When the app is running in the background, EGV notifications may queue up and then "replay" sequentially when the user brings the app to the foreground, causing the Glucose Compass to flicker through previous EGVs. In more severe instances, the app may perceive signal loss and deploy signal loss mitigations. This delay in EGV and alert processing creates a risk that users may miss detection of a hypoglycemic or hyperglycemic event, or make treatment decisions based on outdated glucose information.

    Z-2163-2026 · Root cause: Software design · Recall details · FDA record ↗

  4. Jul 24, 2025Open, Classified

    The affected devices are the Dexcom G7 Continuous Glucose Monitoring System (CGM System) using iOS, watchOS and Android App software (versions 2.8.0 or earlier) and Dexcom ONE+ CGM System using iOS and Android App software (versions 1.4.0 or earlier), henceforth referred to as the App. The affected App does not provide an expected "Sensor Failed" alert when the transmitter sends a "transmitterFailed" error message to the App when the CGM experiences a hardware or firmware failure. Instead, the App ends the CGM sensor session, stops reporting glucose values and displays the Start Sensor screen or No active sensor message without alerting the user, which can lead to missed detection of a hyperglycemic or hypoglycemic event and a delay in treatment.

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

  5. Jul 24, 2025Open, Classified

    The affected devices are the Dexcom G7 Continuous Glucose Monitoring System (CGM System) using iOS, watchOS and Android App software (versions 2.8.0 or earlier) and Dexcom ONE+ CGM System using iOS and Android App software (versions 1.4.0 or earlier), henceforth referred to as the App. The affected App does not provide an expected "Sensor Failed" alert when the transmitter sends a "transmitterFailed" error message to the App when the CGM experiences a hardware or firmware failure. Instead, the App ends the CGM sensor session, stops reporting glucose values and displays the Start Sensor screen or No active sensor message without alerting the user, which can lead to missed detection of a hyperglycemic or hypoglycemic event and a delay in treatment.

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

  6. Jul 24, 2025Open, Classified

    The affected devices are the Dexcom G7 Continuous Glucose Monitoring System (CGM System) using iOS, watchOS and Android App software (versions 2.8.0 or earlier) and Dexcom ONE+ CGM System using iOS and Android App software (versions 1.4.0 or earlier), henceforth referred to as the App. The affected App does not provide an expected "Sensor Failed" alert when the transmitter sends a "transmitterFailed" error message to the App when the CGM experiences a hardware or firmware failure. Instead, the App ends the CGM sensor session, stops reporting glucose values and displays the Start Sensor screen or No active sensor message without alerting the user, which can lead to missed detection of a hyperglycemic or hypoglycemic event and a delay in treatment.

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

  7. 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-1944-2025 · Root cause: Nonconforming Material/Component · names 3 of these models · Recall details · FDA record ↗

  8. May 5, 2025Open, Classified

    A bug in the 2.7.0 version of the G7 iOS App can cause the app to enter a state where it stops updating the estimated glucose value (EGV) and continues to show this stale EGV. If the user is unaware that the EGVs are not being updated and that glucose alerts will not trigger, there is potential for the missed detection of a hyperglycemic or hypoglycemic event or a treatment decision made based off incorrect data. There is no impact to transmitter communication with concurrently connected displays. A concurrently connected receiver, Apple Watch, and/or insulin pump will continue to receive EGVs directly from the transmitter when the app is in the problematic state. There is no impact to Automated Insulin Dosing (AID) therapy as the AID system continues to receive EGVs directly from the transmitter.

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

Most reported Dexcom G7 problems

Device problems

  • Wireless Communication Problem93,013
  • Protective Measures Problem58,766
  • Detachment of Device or Device Component55,378
  • Low Readings21,477
  • Incorrect, Inadequate or Imprecise Result or Readings16,530
  • Unintended Application Program Shut Down12,262
  • Inappropriate or Unexpected Reset10,764
  • Break8,695

Patient problems

  • No Clinical Signs, Symptoms or Conditions281,115
  • Hyperglycemia32,861
  • Hypoglycemia6,605
  • Foreign Body In Patient3,574
  • Loss of consciousness1,087
  • Dizziness800
  • Nausea748
  • Vomiting736

Dexcom G7 models

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

Recent Dexcom G7 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