Why did my Sentry bill go up? How to find the meter
Sentry bills errors, spans, replays, attachments, logs, monitors and Seer against separate allowances. Find the meter that moved before you cut data. Prices checked on 6 Nov 2026.
| Dimension | Included on Team | Pay-as-you-go rate | Typical cause of a jump |
|---|---|---|---|
| Errors | 50,000 a month | $0.0003625 each from 50,001, falling to $0.00015 past 20 million | One looping error or a noisy SDK integration |
| Spans (tracing) | 5,000,000 a month | $0.000002 each up to 100 million, then $0.0000018 | Tracing sampled at or near 100% |
| Session replays | 50 a month | $0.00375 each up to 5,000, falling to $0.002453 | Replay sampling raised on a busy page |
| Attachments | 1 GB | $0.3125 per GB | Files attached to events |
| Logs | 5 GB | $0.50 per GB | Log capture switched on |
| Profiling | None | $0.0315 per continuous profile hour; $0.25 per UI profile hour | Profiling enabled |
| Cron and uptime monitors | 1 of each | $0.78 per cron monitor; $1.00 per uptime monitor | New monitors added |
| Seer | Not included | $40 per active contributor, billed outside the budget | A second developer opening pull requests in a Seer-enabled repository |
Rates from docs.sentry.io/pricing and inclusions from sentry.io/pricing, both checked 6 Nov 2026. Business has the same inclusions at higher error and span rates. Reserved volume bought ahead costs less per event than pay-as-you-go.
The October invoice reads $174.52 instead of $29, and nobody remembers an incident. In that case, look past errors first. Sentry bills each data category against its own allowance and lets the pay-as-you-go budget pay for whatever passes it, so the line that changed tells you what to fix.
Which Sentry meter made the bill go up?
The Sentry meter that moved shows up in Stats > Usage Stats, which breaks accepted, dropped and filtered volume down by category and project for up to 90 days (event-stream guide, checked 6 Nov 2026). Compare the month of the higher invoice with the month before, one category at a time. A rise in errors points at a loop or a noisy integration, a rise in spans at tracing, and a new Seer line at contributor count. Match the dates to the billing period before drawing conclusions.
On the Errors page, the same guide suggests adding the issue, title, project and count() columns and sorting by count. That view shows whether one issue accounts for most of the error volume. If it does, the cause is a loop, and stopping one error from flooding Sentry fixes the bill at its source.
Trace the charge back to its meter
- InvoiceFind the meter that changed.
- UsageMatch the billing period and project.
- SenderInspect that SDK’s configuration.
How does Sentry pay-as-you-go billing work?
Sentry pay-as-you-go billing charges per event for volume past what your plan and reserved volume include, up to a budget you set. The budget is shared across every category on a first-come, first-served basis, and unused reserved volume expires at the end of each billing month (pricing docs, checked 6 Nov 2026). In Team's first error tier, pay-as-you-go costs 25% more per error than reserved volume: $0.0003625 against $0.00029. Past the budget, data is dropped and not charged.
A bill can therefore rise without a single extra error. Spans or replays can spend the budget first, and the guide to Sentry quota exceeded explains what happens to errors once it is gone. Team and Business include spend notifications and a maximum spend threshold (sentry.io/pricing); setting the threshold is the fastest way to cap next month.
Why did my Sentry bill go up when errors stayed flat?
A Sentry bill that rises while errors stay flat often comes from tracing spans. Team includes 5,000,000 spans a month, and a service handling 2 requests a second with 15 spans each produces 77,760,000 spans in 30 days. The 72,760,000 past the allowance cost $145.52 at $0.000002 each, so a $29 plan becomes a $174.52 invoice (pricing docs, checked 6 Nov 2026). The same volume is the default example in our Sentry pricing calculator.
If you only read errors, set tracesSampleRate to 0 and keep the SDK, as described in turning off Sentry tracing but keeping errors. Check any custom tracesSampler function as well, then compare the next day's span count in Usage Stats.
How much does Sentry Seer add for a small team?
Sentry Seer adds $40 a month per active contributor, billed as its own charge outside the pay-as-you-go budget. An active contributor is anyone who opens 2 or more pull requests in a Seer-enabled repository during the month. GitHub accounts marked [bot] are excluded, and on GitLab every group member counts (pricing docs, checked 6 Nov 2026). For two developers on Team who both open pull requests, that is $29 plus $80, or $109 a month before any overage.
Seer is Sentry's AI debugging agent, and it does work that a plain error tracker doesn't. If you use it every week, the $40 may be the best-spent line on the invoice. If it was enabled once and forgotten, it is the easiest line to remove, and the contributor count resets each month.
What does Sentry cost at 100,000, 500,000 and 1.5 million errors?
Sentry Team costs $47.13 a month at 100,000 errors, $134.65 at 500,000 and $322.15 at 1,500,000 on pay-as-you-go, billed monthly with no other data. Reserved volume bought ahead brings those to $43.50, $113.50 and $263.50. The table uses the per-error rates in Sentry's pricing docs and the $29 monthly Team price on sentry.io/pricing, both checked 6 Nov 2026. It is our arithmetic, not an invoice.
| Dimension | Sentry Team, pay-as-you-go | Sentry Team, reserved volume | Epure Cloud |
|---|---|---|---|
| 100,000 errors a month | $47.13 | $43.50 | $29 (Pro, 200,000 events) |
| 500,000 errors a month | $134.65 | $113.50 | $89 (Scale, 1,500,000 events) |
| 1,500,000 errors a month | $322.15 | $263.50 | $89 (Scale, 1,500,000 events) |
Sentry: Team at $29 billed monthly plus per-error rates from docs.sentry.io/pricing, checked 6 Nov 2026; no spans, replays, attachments or Seer. Reserved figures apply the listed reserved rates to the exact volume. Epure: monthly billing only, errors only, no automatic overage.
The comparison only holds if errors are the whole job. Sentry's Team price also buys 5,000,000 spans, 50 replays and up to 90 days of lookback, while Epure Pro keeps 30 days. Epure tracks errors only, with no tracing, replay, profiling or logs, and it is in Beta. If those other meters are on your invoice because you use them, a tighter sampling rate on Sentry is the cheaper move.
How do you lower a Sentry bill without losing errors?
Lowering a Sentry bill without losing errors means cutting the meter that moved and leaving error capture alone. Set a maximum spend threshold first, so next month is capped while you work. Then fix the cause in the category Usage Stats points to, using the list below. A lower error sampleRate is the last resort, because at 0.1 it drops 9 in 10 of your rare bugs along with the noise.
- Errors from one loop: fix the code path and filter that event with
beforeSend, as in the error-loop guide. - Spans: lower
tracesSampleRate, or set it to0if you never open a trace. - Replays and profiles: lower their sample rates, or remove the integration you don't use.
- Seer: review who counts as an active contributor, or turn it off for repositories where nobody reads its output.
- Steady growth: buy reserved volume, which costs less per event than pay-as-you-go.
Would a flat-price error tracker stop the bill from moving?
A flat-price error tracker stops the bill from moving only if errors are all you need. Epure Cloud is $29 a month for 200,000 events on Pro and $89 for 1,500,000 on Scale, with unlimited seats and no automatic overage. Past the monthly quota, Epure keeps counting and stores the first event of each new or regressed issue, up to a grace of 5% of the quota, then refuses only new fingerprints. Epure keeps your Sentry SDK: you change the DSN.
Transactions, replays and profiles are dropped at ingest, so those meters disappear along with the features. Epure pricing lists both plans and the trial terms. The spike valve explains how one looping error stays one issue, with 100 stored events a minute per error and the rest counted. To compare with your own Sentry volume, run the Sentry pricing calculator.
Questions
Why did my Sentry bill go up with no new errors?
tracesSampleRate.Does Sentry charge for dropped or filtered events?
beforeSend.How does Sentry count a Seer active contributor?
[bot] are excluded; on GitLab, all group members count. The count resets monthly, and Seer is billed outside the pay-as-you-go budget (Sentry pricing docs, checked 6 Nov 2026).