Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-1203-2025

Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001 Recall

Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001

FDA recall Class II

Ongoing

FDA lists this Class II recall for Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1203-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Jan 27, 2025
FDA report date
Feb 26, 2025
Quantity in commerce
N/A
Distribution
See key details
FDA cause
Software design

What is being recalled?

Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001

Affected model & UDI checker

Search the exact identifiers published for Z-1203-2025.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
STK-OR-001Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001Check source noticeNot specified
Not specifiedDexcom G6, Continuous Glucose Monitoring System, REF: STK-OR-001Check source notice00386270000590
FDA code information

All Serial Numbers/UDI: 00386270000590

View the original FDA recall notice

Why was this product recalled?

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.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did Dexcom, Inc. take?

On January 27, 2025, Dexcom issued a "Urgent: Medical Device Correction to affected consignees via E-Mail. Dexcom asked consignees to take the following actions: If available, use the G6 App as primary display device to receive glucose readings and alerts. The G6 transmitter allows simultaneous communication with an iOS or Android device as well as a receiver (see letter for additional details). If using an affected G6 Receiver, check CGM glucose values and glucose trend regularly as CGM glucose values and glucose trend graph information continue to be displayed If you believe you may be experiencing the missed or delayed alarm/alerts issue, the issue can be corrected by shutting down the receiver and then turning it back on. Please navigate to the following webpage: https://www.dexcom.com/g6-receiver-update Please read the information provided on the webpage and any recommended actions regarding a software update for your receiver to permanently resolve this issue.

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology