Continuous resilienceAll features.
Everything a resilience campaign does today: how a campaign is set, what each burst measures, the automatic stops, and what is in the report.
31 features in 8 groups, checked against the product on 14 November 2026.
Setting up a campaign
One verified site
You choose the site from a list of your own verified sites. Every request is a GET of its home page over HTTPS. One campaign runs on a site at a time.
Spike, soak or both
The kinds of burst the campaign may send.
A ceiling of 50 to 1,000 users
A slider in steps of 50; it starts at 200. No burst goes above it.
A daily time budget
5 to 120 minutes of bursts a day, counted in UTC; it starts at 30.
8 hours to 7 days
A campaign lasts 8 hours, 24 hours, 3 days or 7 days, and starts when you create it.
Bursts at uneven times
The next burst is set for a random 30 to 90 minutes after the last.
A spike burst
A random number of users between 40% of the ceiling and the ceiling, for 60 to 180 seconds, shortened to fit what is left of the day's budget.
A soak burst
30 minutes, most of it held at 60% of the ceiling. It needs a daily budget of at least 30 minutes.
You type CONFIRM once
One notice covers every automatic burst of the campaign, and the campaign is refused unless you type CONFIRM. The time of your consent is recorded.
What each burst measures
The figures of a stress run
For each phase the requests, errors and response times; over the burst the error rate, the 95th and 99th percentiles and the slowest request.
Degradation, onset and recovery
How much slower the peak was than the baseline, the first phase in which 1% of requests failed, and whether the site recovered.
A reading every 5 seconds
Kept for each burst.
Automatic stops
A check before every burst
A burst does not start unless a fresh request to the site gets a 2xx answer and your uptime monitoring does not show the site as down.
A stop at 50% errors
After the first 15 seconds, a burst ends itself once half of its requests have failed.
A circuit breaker
Once a minute during a burst the site is checked from outside the test. The burst is halted after two checks in a row that fail (a 5xx answer, a timeout or a network error), two in a row answered 429, or two in a row three times slower than the recent healthy average.
After a halt
The burst is stopped, you are alerted, and the campaign carries on with its next burst.
One burst at a time
A campaign never runs two bursts at once.
Checked again every time
Before each burst the host must still resolve to a public address and the account must still be on Business.
The verdict and the summary
A verdict by fixed rules
Failed when any burst reached 50% errors. Attention when the circuit breaker halted a burst, 5% of a burst's requests failed, the site did not recover, a peak was 3 times slower than its baseline, or a 95th percentile was over 500 ms. Otherwise Pass. A risk rating of Low, Moderate or Elevated goes with it.
Your own stops are not counted
A burst you stopped is not counted as a safety halt.
One AI summary for the campaign
Three short parts: the verdict, what it means and what to check, with whether the circuit breaker stepped in.
The report
A PDF when the campaign ends
Executive summary, the campaign at a glance, risk scorecard, the 95th percentile of each burst over time against the 500 ms line, the error rate over time, a table of the bursts, the automatic halts, trend, scope and method, and recommendations.
Trend inside the campaign
The first finished burst beside the last: more than 20% slower is reported as creep, more than 20% faster as settling.
Controls and alerts
Stop a campaign at any time
Stopping it also stops a burst that is running.
Alerts by email and webhook
Your alert channels get a message when the circuit breaker halts a burst, and a summary when the campaign ends.
Campaign cards
Today's burst minutes, the bursts sent so far, and the times of the last burst and the next.
Ownership and safety
Verified sites only
A run is accepted only for a site of yours whose DNS record has been confirmed, and the site is checked again when the run starts.
Public addresses only
A host that does not resolve to a public address is refused when you ask for the run and again before it starts.
Plans and limits
Business
1,200 minutes of bursts a month across all your campaigns. It is not part of Free or Pro.
Resets on the 1st
Allowances count over the calendar month, in UTC, and reset on the 1st.
A burst that never started is not counted
The minutes of a burst are counted when it starts.
What it does not do.
- It is not disaster-recovery testing: it does not test backups, failover or restore, and it injects no faults.
- A campaign runs once, for up to 7 days. It does not repeat by itself, and one campaign is not compared with another.
- The 500 ms line is fixed. You cannot set targets of your own.
- It requests the home page only, from one region.
- A campaign's report is not part of the combined report.
- It is not a penetration test: nothing is exploited and your application's logic is not tested. We do not offer one.