Skip to content
Recall Observatory FDA recall evidence

Exact FDA event identifier

Event 96091

3 recalled-product records grouped only because every row carries this exact official event ID.

Open FDA event record

Event summary

Timeline bucket
January 27, 2025
Product types
Device
Classifications
Class II
Statuses
Ongoing
Recalling firm wording
Dexcom, Inc.

Dossier provenance

Source snapshots represented here

  • openFDA Device Enforcement Report-date coverage June 20, 2012–July 08, 2026 Known gap: openFDA describes 2004-present coverage, but the current export has no report-date records in this interval.
  • openFDA Device Recall event_date_initiated coverage June 01, 1997–June 30, 2026

Enforcement coverage uses report dates; product initiation dates can precede those bounds. Device-enrichment coverage uses FDA event_date_initiated.

How coverage and grouping work

Complete imported group

Every recalled product in this event

3 official enforcement rows

Product dates, classifications, firms, and source wording remain attached to their individual rows. Opening this dossier never hides products that did not match a prior timeline filter.

device · product 1 of 3

Dexcom G6, Continuous Glucose Monitoring System, REFs: STK-OM-001, STR-OM-001, STR-OR-001

Z-1202-2025
Recall number
Z-1202-2025
Initiated
January 27, 2025
Classification
Class II
Status
Ongoing
Recalling firm
Dexcom, Inc.
Quantity
N/A

App-derived interpretation

Unknown reason.no_named_rule · v1.0.0
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 labels are deterministic app interpretations, not FDA categories.

Official device-enrichment evidence · Sourced

Software design

Compare all device evidence states

Inspect official wording and provenance

Reason for recall

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.

Code information

All Serial Numbers/UDI: 00386270000583

Distribution pattern

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 Kong, Israel, Italy, Korea, Kuwait, New Zealand, Norway, Oman, Poland, Qatar, Saudi Arabia, Singapore, Slovakia, South Africa, Sweden, Turkey, United Arab Emirates.

device · product 2 of 3

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

Z-1203-2025
Recall number
Z-1203-2025
Initiated
January 27, 2025
Classification
Class II
Status
Ongoing
Recalling firm
Dexcom, Inc.
Quantity
N/A

App-derived interpretation

Unknown reason.no_named_rule · v1.0.0
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 labels are deterministic app interpretations, not FDA categories.

Official device-enrichment evidence · Sourced

Software design

Compare all device evidence states

Inspect official wording and provenance

Reason for recall

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.

Code information

All Serial Numbers/UDI: 00386270000590

Distribution pattern

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 Kong, Israel, Italy, Korea, Kuwait, New Zealand, Norway, Oman, Poland, Qatar, Saudi Arabia, Singapore, Slovakia, South Africa, Sweden, Turkey, United Arab Emirates.

device · product 3 of 3

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

Z-1204-2025
Recall number
Z-1204-2025
Initiated
January 27, 2025
Classification
Class II
Status
Ongoing
Recalling firm
Dexcom, Inc.
Quantity
N/A

App-derived interpretation

Unknown reason.no_named_rule · v1.0.0
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 labels are deterministic app interpretations, not FDA categories.

Official device-enrichment evidence · Sourced

Software design

Compare all device evidence states

Inspect official wording and provenance

Reason for recall

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.

Code information

All Serial Numbers/UDI: 00386270001900

Distribution pattern

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 Kong, Israel, Italy, Korea, Kuwait, New Zealand, Norway, Oman, Poland, Qatar, Saudi Arabia, Singapore, Slovakia, South Africa, Sweden, Turkey, United Arab Emirates.

Field note

Send feedback

We'll only use this to respond to your feedback.