Continuous resilienceConfirm your site keeps holding, burst after burst.
Continuous resilience fires bounded bursts of load at one verified site through a campaign of up to 7 days, so a slide shows up in the trend from the first burst to the last.
Campaigns of 8 hours to 7 days, on Business.
0
safety halts
29 ms
worst burst p95
1.1×
worst degradation
From the sample report: the first burst of a campaign, no errors.
The highlights.
A single test is a snapshot. Sites change every week: a deploy here, a config change there. The question is whether the site still holds, burst after burst.
Four steps. From campaign to trend.
Verify the asset
Every run targets a domain you've proven you own. No testing systems you don't control.
Set the campaign
Choose spike or soak bursts, a user ceiling, a daily time budget and a length from 8 hours to 7 days. Bursts then fire at uneven times, 30 to 90 minutes apart.
Track the trend
We record each burst's response times, degradation, and recovery, and set the first burst beside the last.
Catch the drift
The campaign ends in one report, with a verdict set by fixed rules and an AI summary, so a slow slide shows up as the bursts add up.
The trend, burst after burst.
The report gives the worst burst p95 across the campaign, how many bursts the safety system halted, the degradation and the recovery. One burst is one data point; the value is the line they draw.
Resilience report
Sample reportExample site
Worst burst p95
29 ms
Safety halts
None
Bursts fired
1
Degradation
1.1×
AI summary
A clean opening: the first bounded burst held p95 at 29 ms with zero errors, a negligible 1.1× degradation, and no reason for the automatic safety circuit-breaker to intervene. One burst is a single data point — the value compounds as the campaign fires more over the following days and a real trend emerges. At 29 ms, this may be your CDN edge absorbing the spike; keep in mind it may reflect the CDN rather than your own server.
Performance testing on a schedule. Not a penetration test, and not disaster-recovery testing.
Branded, downloadable, shareable: the PDF carries the same page, ready for a review or a vendor questionnaire.
What a campaign tracks.
Four figures from the sample campaign, and why each one matters.
29 ms
Worst burst p95
The highest 95th-percentile latency of any burst in the campaign, each measured over the whole burst. Watching it from burst to burst is how you spot a slow slide early.
0
Safety halts
How many bursts the automatic circuit-breaker had to stop. Zero means the site stayed well within its limits under repeated bounded pressure.
1.1×
Worst degradation
The largest single-burst slowdown versus baseline. Flat across bursts is the result you want — no resource quietly failing to reset between runs.
500 ms
p95 objective
The latency line every burst is judged against. It is fixed at 500 ms for every campaign; you cannot set your own.
What you get.
- Campaigns of repeated spike and soak bursts, up to 7 days, on Business
- Response times, degradation, and recovery recorded for every burst
- A slow slide in resilience surfaces as the campaign builds
- A trend from the first burst to the last, not a one-off snapshot
- A verdict by fixed rules and an AI summary for the campaign
- See all features ›
Is it the right tool?
A strong fit when
- Your site changes often: frequent deploys, active development.
- You want to see whether the site holds up as well at the end of a week as at the start.
- You want repeated pressure, inside limits you set.
Not the best fit when
- You need your backups, failover or restore tested. That is disaster-recovery testing, and this is not it.
- You need one heavy test, once. Cloud load testing does that.
- You need a penetration test: a person trying to break in. We do not offer one.
Every burst runs inside a peak user ceiling and a daily time budget you set. The site is checked before each burst and once a minute during it: two bad checks in a row halt the burst, and a burst ends itself once half of its requests have failed.
Included in Business.
Business
Resilience campaigns of up to 7 days, 1,200 minutes of bursts a month, 100 sites
$199 a month₹19,499 a month in India
In more detail.
What continuous resilience tracks
Most tests are a single snapshot. Continuous resilience sends repeated bursts of load at one domain you have verified you own and records each one: its response times, its degradation under load, and its recovery — whether response times come back near the baseline after each bounded burst of pressure. The point is to see, from burst to burst, when your site starts to hold up less well. It also runs behind automatic safety checks that will not start a burst if your site is already struggling, and will stop one that goes badly.
How it works
A campaign lasts 8 hours, 24 hours, 3 days or 7 days and fires bounded bursts at uneven times, 30 to 90 minutes apart, recording how each one goes. A later burst that is slower than an earlier one, or one that does not recover, shows up in the campaign's trend. A single burst is one data point; the value is the line those points draw through the campaign. A campaign runs once: to keep watching, start another. It is available on the Business plan.
When to run one, and what's in the report
It suits a site that changes often — frequent deploys, active development. The report, ready when the campaign ends, is a downloadable, branded PDF: the worst burst p95 across the campaign, how many bursts the safety system had to halt, the degradation, the recovery, and an AI summary of the verdict and what to check. Example result: a first bounded burst at a 29 ms p95 with zero errors and no safety halt. If your site sits behind a CDN, a strong result may reflect the CDN rather than your own server — keep that in mind.
What continuous resilience is not
It is performance testing on a schedule — not a penetration test, and not disaster-recovery failover or restore testing. It tracks how your site performs and recovers under repeated load; it does not test your backups, your failover, or data restoration. A penetration test is a separate, human-led engagement. BCDRPulse does not offer one.
Questions people ask first.
Is this a penetration test?
No. Continuous resilience is automated performance testing on a schedule — repeated bounded load bursts over time. It attempts no exploitation and tests no application logic. A penetration test is a separate, human-led engagement. BCDRPulse does not offer one.
What's the automatic safety system?
A set of checks before and during every burst. A burst won't start if the site is already unwell. While one runs, a circuit-breaker checks the site once a minute from outside the test and halts the burst after two bad checks in a row, and the burst ends itself once half of its requests have failed — so the campaign tests resilience without becoming the cause of an outage.
Why does it run repeatedly instead of once?
A single test is a snapshot. Resilience is about the trend — whether your site holds up as well on the last burst as on the first. Repeated bursts through a campaign of up to 7 days surface that drift early, while it's still cheap to fix.
Does it work behind a CDN like Cloudflare?
Yes. Where a CDN absorbs the bursts at its edge, the result reflects the edge rather than your own server — keep that in mind when reading the numbers.
Does continuous resilience test my backups or failover?
No. It tracks how your site performs under repeated load and whether its response times come back to normal afterwards. It does not test backups, failover, or data restoration — that is disaster-recovery testing, which is a different thing.
How is this different from uptime monitoring?
Uptime monitoring tells you whether your site is up. Continuous resilience repeatedly tests how well it holds up and recovers under load, and shows whether that is getting better or worse through the campaign.
How would I notice resilience slipping?
A later burst that is slower, degrades more, or fails to recover where earlier bursts did not — the early sign that something has weakened. You see it in the campaign's trend, which sets the first burst beside the last.
Know it still holds.
Signing up is free and starts uptime monitoring for 10 sites. Running continuous resilience needs the Business plan.
- A 29 ms worst burst p95, 1.1× degradation and no safety halts are the figures in the sample report, not a customer's site.
- Introductory prices, before GST or VAT. Regular prices are $99 and $399 a month (₹9,699 and ₹38,999 in India).