Recall Record

San Diego, CA, United States

Dexcom, Inc. recalls

10 recalls recorded since 2018, most recently on 27 May 2026. 7 are listed as ongoing. Status and classification are as published by the FDA.

Recalls10
Ongoing (FDA)7
Terminated or completed3
Class I (FDA)3

Ongoing Class II Medical devices

Recall started
27 May 2026
Reason
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.
Distribution
Dexcom does not have distribution records for this product due to its unauthorized release. However Dexcom is able to identify sensor session starts for the affected lots through the Dexcom G7 CGM App user performance data. Based on App user performance data, Lot 1725204004 has sensor session start
Initiated
Voluntary: Firm initiated
Recall number
Z-2574-2026

Ongoing Class II Medical devices

Recall started
14 April 2026
Reason
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.
Distribution
SW12300 & SW13355 Dexcom G7 iOS and watchOS app versions 2.9.0 through 2.11.2: Worldwide - US Nationwide including in the states of AK, AL, AR, AZ, CA, CO, CT, DC, DE, FL, GA, HI, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NJ, NM, NV, NY, OH, OK, OR, PA, PR, RI, SC,
Initiated
Voluntary: Firm initiated
Recall numbers
Z-2164-2026, Z-2163-2026, Z-2165-2026

Ongoing Class I Medical devices

Recall started
28 August 2025
Reason
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).
Distribution
This product was distributed throughout the US. G6 Android US v1.15.0 SW11678 G6 and G6 Pro Android app release has been halted <1% rollout after this issue was identified. Please see the attached consignee data for additional details.
Initiated
Voluntary: Firm initiated
Recall number
Z-0318-2026

Ongoing Class I Medical devices

Recall started
24 July 2025
Reason
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.
Distribution
SW12299 G7 Android CGM App Worldwide Distribution - US Nationwide and the countries of Andorra, United Arab Emirates, Austria, Australia, Belgium, Bahrain, Canada, Switzerland, Czech Republic, Germany, Denmark, Estonia, Spain, Finland, France, United Kingdom, Hong Kong, Ireland, Israel, Iceland, I
Initiated
Voluntary: Firm initiated
Recall numbers
Z-2446-2025, Z-2449-2025, Z-2448-2025, Z-2450-2025, Z-2447-2025

Ongoing Class I Medical devices

Recall started
12 May 2025
Reason
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.
Distribution
worldwide distribution - US Nationwide and the countries of Andorra, Argentina Australia, Austria, Bahrain, Belgium, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Greece, Hong Kong, Ireland, Israel, Italy, Japan, Korea, Latvia, Liechtenstein, Lithuania, Luxembourg, M
Initiated
Voluntary: Firm initiated
Recall numbers
Z-1945-2025, Z-1946-2025, Z-1943-2025, Z-1944-2025

Ongoing Class II Medical devices

Recall started
5 May 2025
Reason
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.
Distribution
Worldwide Distribution: US (nationwide) and OUS (foreign) to countries of: United Arab Emirates (AE), Austria (AT), Australia (AU), Belgium (BE), Bahrain (BH), Canada (CA), Switzerland (CH), Czech Republic (CZ), Germany (DE), Denmark (DK), Spain (ES), Finland (FI), France (FR), United Kingdom (GB),
Initiated
Voluntary: Firm initiated
Recall number
Z-1906-2025

Ongoing Class II Medical devices

Recall started
27 January 2025
Reason
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.
Distribution
Worldwide - US Nationwide distribution in the states of OH, TX, PA, MN, SC, NH, FL, CA, NJ, PR, GA and the countries of Austria, Belgium, Canada, Switzerland, Germany, Spain, France, Ireland, Japan, Netherlands, Slovenia, United Kingdom, Australia, Czech Republic, Denmark, Finland, France, Hong Kon
Initiated
Voluntary: Firm initiated
Recall numbers
Z-1203-2025, Z-1202-2025, Z-1204-2025

Terminated Class II Medical devices

Recall started
3 February 2020
Terminated
20 January 2022
Reason
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.
Distribution
World-wide Distribution
Initiated
Voluntary: Firm initiated
Recall numbers
Z-1562-2020, Z-1560-2020, Z-1561-2020

Terminated Class II Medical devices

Recall started
19 November 2019
Terminated
22 August 2023
Reason
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.
Distribution
US Nation-wide OUS: Austria; Belgium; Canada; Czechia; Denmark; Finland; Germany; Great Britain; Hong Kong; Ireland; Italy; Luxembourg; Netherlands; Norway; South Africa; Spain; Sweden, and Switzerland.
Initiated
Voluntary: Firm initiated
Recall number
Z-1104-2020

Terminated Class II Medical devices

Recall started
12 July 2019
Terminated
15 December 2022
Reason
It has been reported that use of the mobile receiver with software version SW10617 rev 4.0.1.048 have reported: 1. the receiver becoming stuck on initialization screen when powering on. This will cause patients not to be able to receive glucose values or alerts; 2. Reinitialization of the receiver without user interaction. If this occurs, the receiver will either reboot and operate normally or require the user to press the Select button on the receiver in order to resume normal operation. In this situation, the user is provided an audio and vibratory alert every 5 minutes. Until the select button is pressed, patients will not receive glucose values or alerts.
Distribution
US Nationwide distribution.
Initiated
Voluntary: Firm initiated
Recall number
Z-0929-2020

A terminated FDA recall means the FDA has determined that all reasonable efforts to remove or correct the product have been made. What statuses mean.