Dexcom G7 recallZ-1906-2025 · Dexcom, Inc. · initiated May 5, 2025
Open, Classified
Is my device affected?
- Compare the model, catalog and lot or serial numbers on your device or its packaging with the code information below. A recall usually covers only specific models or lots.
- If yours is listed, follow the instructions from Dexcom, Inc. or your healthcare provider. The company's action is summarized under what the company is doing.
- Do not stop using a prescribed or implanted device on your own — talk to your healthcare provider first.
Where to find your model and lot numbers · What recall classes and statuses mean
Why it was recalled
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.
FDA root cause category: Software design
What the company is doing
On May 05, 2025, Dexcom issued a "Urgent Warning" Recall notification to affected consignees via application update. Dexcom asked consignees to take the following actions: 1. Upgrading from app version 2.7 is mandatory and app version 2.7 is no longer available for use. 2. If you need assistance, contact Technical Support. Local Tech Support contact information is available at Dexcom.com Please note that US customers should utilize one of the following options for support. " Phone - 1-844-478-1600 " Call Back request Call Back Request Form " Web Form - https://dexcom.custhelp.com/app/webform " Live chat - https://dexcom.custhelp.com/app/chat/chat_avail If you have any questions, call 858-200-0200 or email: [email protected].
Recall details
- Recall number
- Z-1906-2025
- Status
- Open, Classified
- Initiated by the company
- May 5, 2025
- Posted by the FDA
- Jun 4, 2025
- Recalling firm
- Dexcom, Inc.
- Quantity
- 61,355 users
- Product code
- QBJ
- FDA submissions
- K231081
- 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), Hong Kong (HK), Ireland (IE), Israel (IL), Iceland (IS), Italy (IT), Jordan (JO), Korea, Repulic (KR), Kuwait (KW), Lebanon (LB), Lithuania (LT), Luxemburg (LU), Malta (MT), Netherlands (NL), Norway (NO), New Zealand (NZ), Oman (OM), Poland (PL), Portugal (PT), Qatar (QA), Saudi Arabia (SA), Sweden (SE), Slovenia (SI), Slovakia (SK), Turkey (TR) and South Africa (ZA).
Product description
Dexcom G7 iOS Application, Ref: SW12300 used in conjunction with the Dexcom G7 Continuous Glucose Monitoring (CGM) system
Code information (models, lots, serial numbers)
Software version 2.7.0/ UDI: 00386270001863
Devices named in this recall
1 device in the FDA device registry whose identifier appears in the recall's code information.
- Dexcom G7 iOS App SW12300Dexcom, Inc. · Integrated Continuous Glucose Monitoring System, Factory Calibrated3 recalls1 death55,219 reports
Product lines
Sources and updates
- Recall record: FDA Medical Device Recalls, file dated Oct 16, 2026 · View the FDA recall notice ↗
- Devices: FDA GUDID, file dated Oct 13, 2026. Devices are linked when their identifier (with a valid check digit) appears in the recall's code information.
- Page last rebuilt: Oct 16, 2026. Text above is shown as published by the FDA.
How recalls are matched to devices · Editorial policy · Report an error on this page