Describe the bug
Since approximately May 2026, I have repeatedly experienced Critical Pod Fault 203 (0xCB) when using Omnipod DASH with Loop.
Before May, I had never experienced this fault. It now occurs with almost every Pod. Some Pods complete their full lifetime, but most affected Pods fail during the third day, sometimes with 10 to 14 hours or less remaining. I have also noticed that the fault sometimes occurs when the reservoir is getting low.
When the fault occurs, insulin delivery is interrupted and the Pod must be replaced.
I have seen numerous users reporting the same problem in Facebook Loop communities. I have also read the LoopDocs information about the significantly increased frequency of Fault 203 with newer Atlas DASH Pods.
Attach an Issue Report
I will attach the Issue Report generated through:
Loop Settings → Issue Report
I will also attach a screenshot of the detailed Pod fault information.
To Reproduce
The problem cannot be reproduced reliably because it does not occur with every Pod.
- Activate a new Omnipod DASH Pod in Loop.
- Use the Pod normally in closed loop mode.
- Continue using the Pod into its third day.
- A Critical Pod Fault 203 occurs unexpectedly.
- Insulin delivery is interrupted and the Pod must be replaced.
Expected behavior
The Pod should continue delivering insulin normally until its scheduled expiration without producing a Critical Pod Fault 203.
Screenshots
The attached screenshot shows one recent example with the following information:
Pod time: 71 hours, 36 minutes
Fault time: 71 hours, 33 minutes
Reservoir level: 26.70 U
Fault: Critical Pod Fault 203 (0xCB)
Fault event info: 009 (0x09)
Occlusion type: 0
Immediate bolus in progress: false
Reference: 19-00971-17126-203
Insulin delivery status: Interrupted
Phone
Hardware: iPhone 17 Pro Max
OS Version: 26.5.1
Loop Version
Version Number: 3.13.1 (57)
Repo: LoopKit/Loop
CGM
Device: Dexcom G7
Manager app: Direct to Loop
Pump
Manufacturer: Insulet
Model: Omnipod DASH
Firmware version: Not known
Additional context
The issue started around May 2026 and has become increasingly frequent. It now affects almost every Pod, although some Pods still complete their full lifetime normally.
Could you please clarify:
- Is the underlying cause of these recurring Fault 203 failures already known?
- Is this related to the newer Atlas DASH Pods?
- Could my iPhone 17 Pro Max or its Bluetooth implementation contribute to the problem?
- Is any software mitigation currently being developed or tested?
- Could updating from Loop 3.13.1 to the current main release reduce the frequency of these faults?
- Is an update specifically addressing Fault 203 planned?
- What additional diagnostic information, Pod lot numbers or failed Pod data would be useful?
These repeated failures are concerning because insulin delivery stops completely, the remaining insulin is lost and the Pod must be replaced immediately.
Thank you for your work and for investigating this issue.
Describe the bug
Since approximately May 2026, I have repeatedly experienced Critical Pod Fault 203 (0xCB) when using Omnipod DASH with Loop.
Before May, I had never experienced this fault. It now occurs with almost every Pod. Some Pods complete their full lifetime, but most affected Pods fail during the third day, sometimes with 10 to 14 hours or less remaining. I have also noticed that the fault sometimes occurs when the reservoir is getting low.
When the fault occurs, insulin delivery is interrupted and the Pod must be replaced.
I have seen numerous users reporting the same problem in Facebook Loop communities. I have also read the LoopDocs information about the significantly increased frequency of Fault 203 with newer Atlas DASH Pods.
Attach an Issue Report
I will attach the Issue Report generated through:
Loop Settings → Issue Report
I will also attach a screenshot of the detailed Pod fault information.
To Reproduce
The problem cannot be reproduced reliably because it does not occur with every Pod.
Expected behavior
The Pod should continue delivering insulin normally until its scheduled expiration without producing a Critical Pod Fault 203.
Screenshots
The attached screenshot shows one recent example with the following information:
Pod time: 71 hours, 36 minutes
Fault time: 71 hours, 33 minutes
Reservoir level: 26.70 U
Fault: Critical Pod Fault 203 (0xCB)
Fault event info: 009 (0x09)
Occlusion type: 0
Immediate bolus in progress: false
Reference: 19-00971-17126-203
Insulin delivery status: Interrupted
Phone
Hardware: iPhone 17 Pro Max
OS Version: 26.5.1
Loop Version
Version Number: 3.13.1 (57)
Repo: LoopKit/Loop
CGM
Device: Dexcom G7
Manager app: Direct to Loop
Pump
Manufacturer: Insulet
Model: Omnipod DASH
Firmware version: Not known
Additional context
The issue started around May 2026 and has become increasingly frequent. It now affects almost every Pod, although some Pods still complete their full lifetime normally.
Could you please clarify:
These repeated failures are concerning because insulin delivery stops completely, the remaining insulin is lost and the Pod must be replaced immediately.
Thank you for your work and for investigating this issue.