Epure

Tools/Error storm simulator

Error storm simulator

Enter the errors left in your quota and the size of a burst. The simulator shows how many errors fall outside the quota, and when a steady burst would reach it.

Illustrative model · No traffic sent · Shareable scenario

Build your storm

Example scenarios

Start with the errors left in your quota. Add a burst and see how much falls outside it.

What this models

A quota-capacity scenario at a constant event rate. It does not predict vendor rejection decisions, dynamic spike protection, SDK sampling, or spend caps. Events beyond the included quota may be billed or rejected depending on your account settings. No errors are sent to your application.

Your quota · Under this scenario

260,500

errors beyond the included quota

Beyond quota does not automatically mean lost. Billing and collection depend on your account settings.

Within quota
39,500
Beyond quota
260,500

At a constant rate, you reach the remaining quota in 15 min 48 sec.

Estimate the spike’s cost

On Epure, the loop stays one issue.

Epure stores up to 100 identical events a minute per error and 150 per throw site, then counts the rest. A different error keeps its own budget. Past the monthly quota, new issues are still stored within a 5% grace, and nothing is billed automatically. How the spike valve works.

Keep the SDK. Try a staging project.

Bring exception context to Claude Code or Cursor. Cloud plans have no automatic event overages.

Compare plans
Email this scenario to Epure

Opens your email app with these numbers. Add your stack and questions.

How to use it, the formula & a worked example

What does this tool calculate?

An error storm is a burst of repeated exceptions. This free simulator compares the burst with your remaining included quota; it is a labelled simulation and sends no traffic to your app.

How to use it

  1. Enter the errors left in your monthly quota.
  2. Enter the total errors in the burst and its duration in hours.
  3. Read the volume beyond the quota and the time to reach it.

Formula and result

Beyond quota = max(0, storm errors − remaining quota). When the burst exceeds the allowance, time to quota = remaining quota ÷ storm errors × duration.

Beyond quota means outside the included allowance, not necessarily lost: vendors bill, throttle or drop those errors depending on the plan. The time estimate assumes a constant rate. On Epure Cloud, nothing past the quota is billed and existing issues keep counting.

Worked example

Example: 300,000 errors over 2 hours with 39,500 included errors remaining leaves 260,500 beyond quota. At a constant rate, the allowance is reached in 15 min 48 sec. This does not predict which events a vendor will reject.

Account settings can change collection and billing. Sentry pay-as-you-go behavior. Published by Epure, an exception-tracking provider. No Sentry affiliation. Updated .

Estimate what an error storm costs on Sentry →

Error storm simulator questions

What is an error storm?
An error storm is a burst of repeated exceptions, usually one error looping on every request or render. This simulator compares the burst with the errors left in your monthly quota and shows how many fall outside it. It is a labelled simulation: it sends no traffic to your app.
How is the time to quota calculated?
When the burst is larger than the remaining quota, the simulator divides the remaining errors by the burst size and multiplies by the burst duration. It assumes a constant rate. If the burst fits inside the remaining quota, the quota is not reached during that burst.
Are errors beyond the quota always lost?
No. Depending on the vendor and plan, errors past the quota may be billed as pay-as-you-go, throttled or dropped. Sentry, for example, drops data past your reserved volume and pay-as-you-go budget. This simulator only measures the volume outside your stated allowance.
How does Epure handle an error storm?
Epure stores up to 100 identical events a minute per error and 150 per throw site, then counts the rest, so a loop stays one issue with an exact count. Past the monthly quota, new issues are still stored within a 5% grace and nothing is billed. How the spike valve works.