Peptide basics

Tirzepatide adverse-event reports by year, and what the curve measures

On this page
  1. The series, and the queries behind it
  2. The curve and the launch dates are the same curve
  3. What the pre-approval rows tell you
  4. What is in the reports themselves
  5. Where a denominator does exist
  6. Common questions

Reports filed to the FDA naming tirzepatide products grew steeply between 2022 and 2025.

The products launched during that window, so the number of people taking them grew steeply too. A report count with no denominator cannot separate the two.

The database also contains a handful of reports dated before either product was approved, which shows these are administrative records rather than a clean timeline of events.

Nothing in this series says the drug became more or less risky. It says more reports arrived.

This page describes a time series of report counts and the reasons it cannot be read as a risk trend. It makes no claim about whether tirzepatide is safe or harmful, and it does not advise on symptoms — that requires someone who can examine you.

The series, and the queries behind it

Counting by receipt date on the openFDA adverse event endpoint gives an annual report count per product string. For MOUNJARO in the extract dated 28 April 2026 the yearly totals were 5,015 (2022), 20,691 (2023), 22,001 (2024), 30,388 (2025) and 6,664 for the part of 2026 the extract covers — all counts of reports received, not of verified events.1

For ZEPBOUND in the same extract they were 37 (2023), 10,547 (2024), 30,799 (2025) and 12,190 for the partial 2026 — again reports received, with no denominator attached and no causal assessment behind any of them.2

Under the generic string TIRZEPATIDE the whole record is 2,641 reports, rising from 22 in 2022 to 1,391 in 2025 — two orders of magnitude smaller than the brand strings for the same molecule, which is a fact about how reporters write product names rather than about the molecule.3

The curve and the launch dates are the same curve

Mounjaro's original application, NDA215866, has an approval status date of 13 May 2022. Its report series is negligible before 2022 and 5,015 in the calendar year it launched.51

Zepbound's application, NDA217806, has an approval status date of 8 November 2023. Its report series is 37 for 2023 — the seven weeks it was on the market — and 10,547 for its first full year. Read as risk, that is a 285-fold increase in danger over one new year's eve. Read as uptake, it is a product going on sale.62

  • More people taking a product means more people with something to report.
  • Manufacturers must forward reports that reach them, so a manufacturer with more customers files more reports.
  • Media coverage and litigation advertising raise reporting independently of both.
  • None of these three is visible in the count, and all three moved sharply across this window.78

The shape is also consistent with what has been measured across FAERS generally. Hoffman and colleagues looked at 334,984 reports for 62 drugs approved between 2006 and 2010 and found the typical contemporary pattern is a rise over the first three quarters after approval and then a broadly stable count — a description of reporting behaviour after a launch, not of a hazard that grows and then plateaus.8

What the pre-approval rows tell you

The ZEPBOUND series contains single-digit counts for 2015, 2017, 2018, 2019, 2020, 2021 and 2022 — years entirely before the product existed as an approved drug. MOUNJARO carries similar small counts from 2016 onwards.12

The receipt date records when FDA first received a report in a case series, and a case that is later amended keeps its original receipt date. Together with the duplicate and incomplete reports FDA acknowledges are present, that is enough to put rows in a time series that cannot correspond to events involving the product named. We are not able to reconstruct the origin of any individual one of these rows from the public API.107

What is in the reports themselves

Ranking reaction terms under the generic TIRZEPATIDE string in the same extract puts PRODUCT TAMPERING first at 408 reports, ahead of NAUSEA 327, VOMITING 279 and DIARRHOEA 231 — a ranking that describes what reporters wrote about products, not a hierarchy of physiological effects. Those tampering reports are concentrated in 2024 (175) and 2025 (229).4

A term appearing at the top of a ranked list therefore says nothing about how common the underlying thing is among people taking the drug. It says that reports mentioning it were filed, in a period when compounded and unapproved versions of this molecule were widely discussed.47

Where a denominator does exist

SURMOUNT-1 randomised 2,539 adults with obesity or overweight without diabetes across three tirzepatide groups and placebo for 72 weeks, and reported adverse events against that placebo arm. Adverse events caused treatment discontinuation in 4.3%, 7.1% and 6.2% of participants in the three tirzepatide groups and 2.6% of those receiving placebo.9

Those percentages have a denominator, a comparison group and a defined follow-up window. They are not larger or more alarming than the FAERS counts; they are a different kind of number, and they are the kind that supports a statement about how often something happened.9

Tirzepatide has two approved US products, a phase 3 record and a labelled adverse-reaction table. Where any of those can answer a question, a report count should not be the source quoted.

Common questions

Does the rise from 2023 to 2025 mean tirzepatide became more dangerous?

The data cannot answer that. Report counts rise with the number of people taking a product, with manufacturer reporting obligations and with press attention. None of those are recorded in the count, and the products launched inside this window.

Why is the generic-name total so much smaller than the brand totals?

Because the search matches the product name as written on the report. Reports filed as MOUNJARO or ZEPBOUND do not appear in a query for TIRZEPATIDE, and vice versa.

Can I compare tirzepatide's curve with semaglutide's?

Not as a comparison of risk. The two molecules have different numbers of users, different launch dates, different numbers of brands and different reporting histories, and the counts hold none of that constant.

Sources

  1. Regulatory
    openFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"MOUNJARO"&count=receivedateU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproductBack to text
  2. Regulatory
    openFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"ZEPBOUND"&count=receivedateU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproductBack to text
  3. Regulatory
    openFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"TIRZEPATIDE"&count=receivedateU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproductBack to text
  4. Regulatory
    openFDA drug adverse event endpoint — query: search=patient.drug.medicinalproduct:"TIRZEPATIDE"&count=patient.reaction.reactionmeddrapt.exactU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/event.json?search=patient.drug.medicinalproductBack to text
  5. Regulatory
    Drugs@FDA application NDA215866 (MOUNJARO) — original approval submission and status dateU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/drugsfda.json?search=application_number:%22NDA2Back to text
  6. Regulatory
    Drugs@FDA application NDA217806 (ZEPBOUND) — original approval submission and status dateU.S. Food and Drug Administration, openFDA, 2026api.fda.gov/drug/drugsfda.json?search=application_number:%22NDA2Back to text
  7. Regulatory
    FDA Adverse Event Monitoring System (AEMS) Public Dashboard [formerly FAERS] — limitations to the dataU.S. Food and Drug Administration, 2026www.fda.gov/drugs/questions-and-answers-fdas-adverse-event-reporBack to text
  8. Secondary source
    The Weber effect and the United States Food and Drug Administration's Adverse Event Reporting System (FAERS): analysis of sixty-two drugs approved from 2006 to 2010Hoffman KB, Dimbil M, Erdman CB, Tatonetti NP, Overstreet BM. Drug Safety, 2014 · doi:10.1007/s40264-014-0150-2 · PMID 24643967doi.org/10.1007/s40264-014-0150-2Back to text
  9. Primary study
    Tirzepatide Once Weekly for the Treatment of Obesity (SURMOUNT-1)Jastreboff AM, Aronne LJ, Ahmad NN, et al.. New England Journal of Medicine, 2022 · doi:10.1056/NEJMoa2206038 · PMID 35658024doi.org/10.1056/NEJMoa2206038Back to text
  10. Regulatory
    openFDA: Drug Adverse Event API reference (receivedate field definition)U.S. Food and Drug Administration, openFDA, 2026open.fda.gov/apis/drug/event/Back to text