Sentry Spans and Performance Quota Running Out

Share
Workaround available All Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Tracing burns spans quickly at a high sample rate. Lower tracesSampleRate or use a sampler and watch the Stats page.

Most likely fix: Sample less

How to fix it

Try these in order — the most common fix is first.

  1. 1. Sample less

    1. Set tracesSampleRate to a low value
    2. Use tracesSampler to drop health checks and noisy routes
    Did this fix it?
  2. 2. Monitor

    1. Settings > Stats > filter by Spans
    2. Add a spend notification threshold on Team or Business
    Did this fix it?

Symptoms

Span quota is used up early in the month.

Why it happens

  • tracesSampleRate set to 1.0 in production
  • Chatty background jobs and health checks create many spans

This guide also covers

  • sentry spans quota
  • sentry performance monitoring expensive

Still not working?

If Sentry keeps failing, you're not alone. See every Sentry problem users report or the alternatives people switch to.

We build software. Any software.

Paying for apps that don't quite fit? We build exactly what you need.

We're a small team of developers who build custom software fast. Not just tools like Sentry: web and mobile apps, games, desktop software, AI tools, internal tools: whatever you have in mind. We build and run our own products too: booking platforms, games, learning apps. See our work

  • Web apps & SaaS
  • Mobile apps (iOS & Android)
  • Games
  • Desktop software
  • AI tools & automations
  • Internal tools & dashboards
  • Client portals & booking
  • Your own version of any tool
  • ✓ Free 15-min call to scope it
  • ✓ Price agreed up front
  • ✓ Your data, your code
Fixed it? Share this guide

The same problem in other apps

All slow, laggy or resource-hungry guides →

Other Sentry errors

All 10 Sentry errors and fixes →