Devices › Pump, infusion, insulin, to be used with invasive glucose sensor
Device brand name · Insulin infusion pump
Animas Vibe: medical device reports filed with FDA
88,703 reports name it, 2012–2020. Manufacturer given most often on reports: Animas. Product code OYC.
- 88,703
- device reports naming the brand
- 0.3% of all MAUDE reports · about 6,120 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 98%
- classified as malfunction
- 85.5% across the product code
- 0%
- classified as death, as reported
- 11 reports · not verified by FDA
FDA's MAUDE database holds 88,703 reports that name the brand "Animas Vibe" (insulin infusion pump), received between January 2012 and September 2020; the manufacturer given most often on reports is Animas. Spellings of one product vary from report to report.
0 reports arrived in the 12 months to August 2026, and none in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are malfunction (98%) and injury (1.7%); across all pump, infusion, insulin, to be used with invasive glucose sensor reports (product code OYC) death is recorded in 0.3% and malfunction in 85.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are structural problem (28.4%), image display error/artifact (12.1%) and device displays incorrect message (9.3%). The patient problems coded most often are hyperglycemia, hypoglycemia and polydipsia. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
No report naming Animas Vibe was received in the five years to August 2026; the latest was received in September 2020.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 891,173 reports carrying product code OYC. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Structural problem | 25,200 | 28.4% | 2.6% |
| Image display error/artifact | 10,713 | 12.1% | 1.1% |
| Device displays incorrect message | 8,250 | 9.3% | 24% |
| Crackthe device cracked | 7,405 | 8.3% | 2.2% |
| Moisture damage | 6,001 | 6.8% | 1.5% |
| Breakthe device broke | 5,658 | 6.4% | 10.1% |
| No display/image | 5,522 | 6.2% | 5% |
| Fail-safe problem | 4,941 | 5.6% | 0.5% |
| Poor quality image | 4,525 | 5.1% | 0.2% |
| Electrical /electronic property probleman electrical or electronic problem | 4,378 | 4.9% | 0.6% |
| Failure to prime | 3,288 | 3.7% | 0.5% |
| Failure to read input signal | 3,079 | 3.5% | 0.4% |
| Premature discharge of battery | 1,909 | 2.2% | 0.8% |
| Wireless communication problema wireless connection problem | 1,617 | 1.8% | 1.3% |
| Device operates differently than expectedthe device behaved unexpectedly | 1,424 | 1.6% | 4.5% |
| Device alarm system | 1,421 | 1.6% | 2.4% |
| Incorrect measurementthe device measured wrongly | 1,408 | 1.6% | 1.2% |
| Battery problema problem with the battery | 1,330 | 1.5% | 3.1% |
| Device inoperablethe device could not be used | 1,125 | 1.3% | 2.7% |
| Inaccurate delivery | 724 | 0.8% | 0.3% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Hyperglycemiahigh blood sugar | 1,272 | 1.4% |
| Hypoglycemialow blood sugar | 433 | 0.5% |
| Polydipsia | 304 | 0.3% |
| Nauseafeeling sick | 271 | 0.3% |
| Elevated ketones/ diabetic ketoacidosis | 215 | 0.2% |
| Urinary frequency / polyuria | 145 | 0.2% |
| Confusion/ disorientation | 144 | 0.2% |
| Vomitingbeing sick | 139 | 0.2% |
| Dizzinesslight-headedness or unsteadiness | 119 | 0.1% |
| Dehydrationdehydration | 109 | 0.1% |
| Blurred vision | 85 | 0.1% |
| Abdominal painstomach or belly pain | 71 | 0.1% |
| Lethargysluggishness | 68 | 0.1% |
| Ambulation or postural difficulties | 52 | 0.1% |
| Headachehead pain | 52 | 0.1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Animas Vibe | Product code OYC | All MAUDE reports |
|---|---|---|---|
| Reports | 88,703 | 891,173 | 26,136,888 |
| Share of that pool | — | 10% | 0.3% |
| Classified as death, per 1,000 reports | 0 | 3 | 9 |
| Classified as injury | 1.7% | 14.2% | 36.2% |
| Classified as malfunction | 98% | 85.5% | 62.3% |
| Filed by the manufacturer | 100% | 100% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code OYC
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Paradigm Real-Time Revel Insulin Infusion Pump | 178,691 | 0 | 0.6% |
| Paradigm Real-Time Insulin Infusion Pump | 126,282 | 0 | 0.3% |
| 640G Insulin Pump MMT-1712K | 119,547 | 1,598 | 0.1% |
| 640G Insulin Pump MMT-1711K | 76,609 | 151 | 0.1% |
| T Slim G5 System | 49,783 | 0 | 0% |
| t:slim G4 system | 39,215 | 20 | 0% |
| Pump Mmt-1712kl 640g V4 10 Bk Sf Mg | 21,531 | 952 | 0% |
| 640g Insulin Pump | 16,911 | 0 | 0% |
| Paradigm REAL-Time REVEL Insulin Infusion Pump MMT-723LNAS | 12,936 | 41 | 0.8% |
| t:slim X2 Insulin Pump | 31,159 | 86 | 0% |
| Pump Mmt-1711kl 640g V4 10 Bk Sf Mm | 11,157 | 168 | 0% |
| Paradigm REAL-Time Insulin Infusion Pump MMT-754WWS | 10,465 | 661 | 0% |
| Paradigm Real-Time Revel Insulin Infusion Pump Mmt-723nas | 8,540 | 49 | 0.8% |
| 640g Insulin Pump Mmt-1712b | 5,629 | 1 | 0% |
| Paradigm Insulin Infusion Pump | 16,324 | 0 | 0.4% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Animas Vibe reports
How many FDA reports name Animas Vibe?
88,703 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (98%) and injury (1.7%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
structural problem (28.4%), image display error/artifact (12.1%), device displays incorrect message (9.3%), crack (8.3%) and moisture damage (6.8%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%) and voluntary reports (0%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Animas Vibe was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.