Dexcom G5 Mobile Receiver Kit (Retail)Recalls & reported problems across all models
Dexcom, Inc. · 3 models in the FDA device registry
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 1,659
- Deaths reported
- 0
- Injuries reported
- 5
- Recalls
- 1
We found 3 models of Dexcom G5 Mobile Receiver Kit (Retail) by Dexcom, Inc. in the FDA's device registry (GUDID). Together they are named in 1,659 adverse event reports in the FDA's MAUDE database, received between Aug 17, 2016 and Aug 3, 2020 — classified as 5 injuries, 1,654 malfunctions.
The most frequently reported specific device problem is “Device Displays Incorrect Message” (917 reports).
1 FDA recall record name at least one of these models by its device identifier.
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
Dexcom G5 Mobile Receiver Kit (Retail) 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.
- Jul 12, 2019Terminated
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.
Z-0929-2020 · Root cause: Software design · names 3 of these models · Recall details · FDA record ↗
Most reported Dexcom G5 Mobile Receiver Kit (Retail) problems
Device problems
- Device Displays Incorrect Message917
- Inappropriate or Unexpected Reset241
- Wireless Communication Problem129
- Unable to Obtain Readings122
- Device Inoperable89
- Defective Alarm81
- No Audible Alarm30
- Unexpected Shutdown27
Patient problems
- No Consequences Or Impact To Patient1,654
- Hypoglycemia2
- Loss of consciousness2
- Fracture, Arm1
- Hyperglycemia1
- Malaise1
- Vomiting1
Dexcom G5 Mobile Receiver Kit (Retail) models
3 models, most reported first. Each model has its own page with its reports, recalls and device details.
- Dexcom G5 Mobile Receiver Kit (Retail) STK-RF-001Sensor, Glucose, Invasive1 recall980 reports
- Dexcom G5 Mobile Receiver Kit (Retail) STK-RF-BLUSensor, Glucose, Invasive1 recall368 reports
- Dexcom G5 Mobile Receiver Kit (Retail) STK-RF-PNKSensor, Glucose, Invasive1 recall311 reports
Recent Dexcom G5 Mobile Receiver Kit (Retail) adverse event reports
The 15 most recent reports across all models, in the reporter's own words as published by the FDA.
MalfunctionAug 3, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 10359463 ↗MalfunctionJun 25, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 10194529 ↗MalfunctionJun 1, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 10105132 ↗MalfunctionApr 23, 2020Inappropriate or Unexpected Reset; Inappropriate or Unexpected Reset
IT WAS REPORTED THAT THE RECEIVER INITIALIZED WITHOUT A MANUAL RESTART OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9991025 ↗MalfunctionMar 31, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. THE PRODUCT WAS EVALUATED. AN EXTERNAL VISUAL INSPECTION WAS PERFORMED AND PASSED. CHARGE AND BOOT TESTS WAS PERFORMED AND PASSED. FUNCTIONAL TESTS WAS PERFORMED AND PASSED RELEVANT TESTING. THE RECEIVER LOG WAS DOWNLOADED AND REVIEWED FINDING ERROR RELATED TO COMPLAINT. THE ALLEGATION WAS CONFIRMED. THE PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9903095 ↗MalfunctionMar 17, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9844651 ↗MalfunctionJan 29, 2020Unable to Obtain Readings; Unable to Obtain Readings
IT WAS REPORTED THAT ERROR ICON DISPLAYED OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9642298 ↗MalfunctionJan 18, 2020Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT SIGNAL LOSS OVER ONE HOUR OCCURRED. A REVIEW OF THE SHARE LOGS WAS PERFORMED AND A LOSS OF CONNECTION WAS NOT FOUND WITHIN THE INVESTIGATION WINDOW. THE ALLEGATION WAS NOT CONFIRMED. THE PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9604784 ↗MalfunctionJan 2, 2020Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT SIGNAL LOSS OVER ONE HOUR OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9538762 ↗MalfunctionDec 16, 2019Inappropriate or Unexpected Reset; Inappropriate or Unexpected Reset
IT WAS REPORTED THAT THE RECEIVER INITIALIZED WITHOUT A MANUAL RESTART OCCURRED. DATA WAS PROVIDED FOR INVESTIGATION BUT DOES NOT REFLECT THE ALLEGED DEVICE. CONFIRMATION OF THE COMPLAINT WAS UNDETERMINED. THE PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9474358 ↗MalfunctionDec 11, 2019Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT SIGNAL LOSS OVER ONE HOUR OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9453314 ↗MalfunctionDec 11, 2019Unexpected Shutdown; Unexpected Shutdown
IT WAS REPORTED THAT UNEXPECTED RECEIVER SHUTDOWN OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9450095 ↗MalfunctionDec 3, 2019Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT SIGNAL LOSS OVER ONE HOUR OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9405633 ↗MalfunctionNov 25, 2019Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT A LOSS OF CONNECTION OCCURRED. NO DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ISSUE WAS UNDETERMINED. THE PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9370039 ↗MalfunctionNov 16, 2019Wireless Communication Problem; Wireless Communication Problem
IT WAS REPORTED THAT SIGNAL LOSS OVER ONE HOUR OCCURRED. NO PRODUCT OR DATA WAS PROVIDED FOR EVALUATION. CONFIRMATION OF THE ALLEGATION AND A PROBABLE CAUSE COULD NOT BE DETERMINED. NO INJURY OR MEDICAL INTERVENTION WAS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9333295 ↗
Other Dexcom, Inc. products
- Dexcom G613 models · 637,302 reports · 7 recalls
- Dexcom G6 Transmitter2 models · 469,968 reports
- Dexcom G732 models · 325,909 reports · 8 recalls
- Dexcom G521 models · 206,314 reports · 1 recall
- Dexcom G7 GSS (161)4 models · 141,244 reports · 1 recall
- Dexcom G4 Platinum41 models · 119,308 reports · 2 recalls
- Dexcom G7 Receiver4 models · 33,732 reports · 1 recall
- Dexcom G7 GSS (160)4 models · 33,558 reports
Sources and updates
- Models: FDA GUDID, file dated Oct 13, 2026. Models are grouped by the brand name the manufacturer registered.
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 16, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page