Cloud stress testingAll features.
Everything a Cloud stress test does today: the four profiles, each figure it measures, the controls that keep it safe, and what is in the report.
34 features in 8 groups, checked against the product on 14 November 2026.
Setting up a run
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.
Four profiles
Gradual, aggressive, spike and soak. Gradual is the one it starts on.
A peak of 50 to 1,000 users
A slider in steps of 50; it starts at 200.
1 to 60 minutes
For the gradual, aggressive and spike profiles; it starts at 5 minutes.
A soak of up to 4 hours
The soak profile runs from 1 minute to 4 hours and holds 60% of the users you chose, for most of the run.
Four measured phases
After a short warm-up that is not measured: a baseline held at a low level, a climb, the peak held, and a recovery back down to the baseline level.
How the time is divided
Baseline, climb, peak and recovery take 15, 30, 40 and 15% of a gradual run; 10, 15, 60 and 15% of an aggressive one; 20, 5, 55 and 20% of a spike; and 5, 10, 80 and 5% of a soak.
The baseline level
10% of the peak; 5% for a spike and 20% for a soak.
Run now or book for later
A single run can be booked for a time up to 14 days ahead.
What it measures
Figures for each phase
Requests, errors, the error rate, requests per second, the average, median and slowest response time, and the 90th, 95th and 99th percentiles.
A reading every 5 seconds
Requests, errors, the error rate, requests per second, the average and the 95th percentile.
Totals for the run
The same figures over the four measured phases together.
Degradation factor
The 95th percentile at the peak divided by the 95th percentile at the baseline. The baseline is marked unreliable when it had fewer than 30 requests.
Error onset
The first phase in which 1% of requests or more failed.
Recovery
Yes or no: whether the 95th percentile in the recovery phase came back within 1.25 times the baseline's.
Safety controls
You type CONFIRM
Before a run, and before booking one, a notice says the test may slow the site or take it offline, and the run is refused unless you type CONFIRM. The time of your consent is recorded with the run.
An Abort button
A running test of yours can be stopped from its card; the cloud machine is stopped and the test is marked as aborted.
A run that hangs is closed
A run with no result 30 minutes after it should have ended is marked as failed.
The rating and the summary
A risk rating by fixed rules
Elevated when 5% of requests or more failed, over the run or at the peak, when the site did not recover, or when the peak was 3 times slower than a reliable baseline. Moderate at 0.5% failed or 1.5 times slower. Otherwise Low. AI does not decide it.
A hint about firewalls
When requests were already failing at the baseline, the report says a firewall, a CDN rule or bot protection may have refused them.
An AI summary
Three short parts: the verdict, what it means and what to check. It has to agree with the rating, and it is told to say when a CDN may have answered in place of your server.
The report
A PDF with charts
The 95th percentile and the average over time, with the phases marked and the baseline drawn as a line; requests per second over time; and the 95th percentile for each phase.
Its sections
Cover, executive summary, risk scorecard, performance summary, the charts, a table of the phases, degradation and recovery, recommendations, trend, and two appendices of raw figures.
Trend
Beside the previous finished run.
Combined report
On the Reports page up to 50 reports, from this product and the others, can be merged into one PDF with a cover and a contents page.
History
The page shows your 10 most recent runs.
Queue and controls
One test at a time
A second cloud stress test cannot be started while one of yours is queued or running.
Cancel a queued run
From the Jobs page.
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
20 cloud stress tests a month. 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 booked run counts when it runs
It is counted in the month it runs in.
Our failures are not counted
A run that never started, or failed on our side, does not use the allowance.
What it does not do.
- It does not search for the breaking point by itself. It climbs to the peak you choose and holds it.
- A single run does not stop by itself when the site struggles: it runs to the end unless you press Abort. Resilience campaigns have automatic stops.
- Recovery is a yes or a no, not a time.
- It records a failure as an answer that was not 2xx, with no count for each status code.
- It requests the home page only, from one region.
- It is not disaster-recovery testing: it does not test backups, failover or restore.
- It is not a penetration test: nothing is exploited and your application's logic is not tested. We do not offer one.