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

Omnipod 5 Pods. Recall

Omnipod 5 Pods. Model/Catalog number: PT-001662 ASM 5PK Pod STRL OPS G6G7

FDA recall Class I

Ongoing

FDA lists this Class I recall for Omnipod 5 Pods.. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1797-2026
Recall classification
Class I
Enforcement status
Ongoing
Initiation date
Mar 12, 2026
FDA report date
Apr 22, 2026
Quantity in commerce
1,240,115 units
Distribution
See key details
FDA cause
Process design

What is being recalled?

Omnipod 5 Pods. Model/Catalog number: PT-001662 ASM 5PK Pod STRL OPS G6G7

Affected model & UDI checker

Search the exact identifiers published for Z-1797-2026.

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
PT-001662Omnipod 5 Pods.Check source noticeNot specified
Not specifiedOmnipod 5 Pods.Check source notice10385083000527
FDA code information

Model/Catalog number: PT-001662 ASM 5PK Pod STRL OPS G6G7. UDI-DI: 10385083000527. Lot Codes: PH1U02252541, PH1U03282511, PH1U03282522, PH1U03312511, PH1U03312521, PH1U04012511, PH1U04012521, PH1U05052511, PH1U08162531, PH1U08182531, PH1U08182541, PH1U09242511, PH1U09242521, PH1U09242531, PH1U09252521, PH1U09252531, PH1U10152541, PH1U10162531, PH1U10162541, PH1U10172531, PH1U10172541, PH1U10182531, PH1U10182541, PH1U10202511, PH1U10202521, PH1U10202531, PH1U10202541, PH1U10212531, PH1U10212541, PH1U10222531, PH1U10222541, PH1U10232531, PH1U10232541, PH1U10242521, PH1U10242531, PH1U10242541.

View the original FDA recall notice

Why was this product recalled?

Due to a manufacturing defect, certain Omnipod 5 Pods from 49 lots have an internal soft cannula tear that results in insulin leaking into the Pod instead of being delivered to the user regardless of basal or bolus delivery. This defect results from damage to the unexposed portion of the soft cannula during manufacturing, which would result in a compromised fluid path. The primary failure mode is pump under-delivery due to loss of insulin to an internal leak; in some cases, the defect may also lead to pump shutoff and cessation of insulin delivery when leaked insulin contacts Pod circuity in a manner that results in an electrical short. Under-delivery of insulin (both basal and bolus insulin) or cessation of insulin put users at risk of hyperglycemia, and complications from acute and chronic hyperglycemia, including dehydration, blurry vision, nausea, vomiting, altered mental status, diabetic ketoacidosis (DKA), hyperglycemic hyperosmolar syndrome (HHS), or even death. Users may require hospitalization or medical intervention to treat severe adverse health consequences. Not all devices with the defect will issue an alarm or alert the user. If there is sufficient leakage of insulin to cause a short in the circuity, the Pod will issue a Hazard Alarm that stops all insulin delivery and alerts the user to replace their Pod. In addition, if a user s glucose is trending high and is not responding to insulin delivery, the system may reach the maximum amount of insulin microboluses allowed by the system and trigger the Automated Delivery Restriction (ADR) alert that tells users to check their blood glucose and take appropriate actions (i.e., ADR is a response to persistent hyperglycemia and maximum automated delivery constraints rather than a direct detection of the leak). The magnitude of under-delivery is unknown and based on multiple factors, including how much insulin is being delivered, whether an alarm and/or alert triggers, whether and when the user recognizes the device defect, the duration of Pod use, and the size of the tear.

What actions did Insulet Corporation take?

Insulet notified consignees via press release and letters sent via email primarily and also text message on 03/12/2026. The press release instructed users to visit omnipod.com/check-pods to confirm whether their Pod lot number is affected, discontinue use of any affected pods and replace it with a Pod from an unaffected lot. Consignees were asked to contact Insulet to arrange for the return of any affected Pods on hand. Patients were directly notified and instructed to visit omnipod.com/check-pods to acknowledge receipt and check to see if their lot is affected, DO NOT use Pods from the affected lots, discontinue use of any impacted Pod immediately, and contact Insulet to request replacement Pods and return unused Pods from affected lots. Healthcare providers were also directly notified and informed that Insulet will be replacing the pod supply for affected customers, and that if patients do experience a temporary interruption in pod supply, we are advising them to reach out to their healthcare provider for guidance on alternative insulin delivery options until replacement Pods are received. They were also advised of the communication and instructions sent to patients and were advised that if their patients contact them regarding the issue to advise them as follows: visit omnipod.com/check-pods to acknowledge receipt and check to see if their lot is affected, DO NOT use Pods from the affected lots, discontinue use of any impacted Pod immediately, and contact Insulet to request replacement Pods and return unused Pods from affected lots. For product support, replacement requests, or to report adverse events or quality concerns related to Omnipod 5 Pods, please contact Insulet Product Support at 1-800-641-2049, available 24/7.

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