Frequently asked questions.

An enterprise platform for authorized DDoS resilience testing: controlled, distributed load against infrastructure you own, a live console while it runs, and a report you can export as PDF when it ends.

You build a test plan of up to your package's step limit, pick the regions it runs from, and start it now or put it on a schedule. The load comes from cloud machines we launch in those regions for that run and shut down when it ends.

82 types in eight families: HTTP(S), TCP, TLS/SSL, DNS, slow connections, UDP, ICMP, and MQTT, across layers 3, 4, and 7. You see the full list when you build a test plan.

Yes. A step can run for as little as 30 seconds. Test time is reserved in whole hours when a run starts, so a 20-minute run uses one hour. If you stop early, any whole hours you did not use go back to your balance.

Yes. A test can repeat every set number of hours, days, weeks, or months. Before saving, the schedule is checked against your remaining test time and the length of the test, so it cannot overrun your package.

Only your organization, and only against targets our team has registered to it. Inside your team, admins and members with the Attacker role can build, schedule, start, and stop tests. Observers can follow runs and read results, but cannot start or change anything.

Yes. From the console you can stop the whole run, stop only the current step, or move on to the next one. Stopping asks for a single confirmation, so it never happens by accident.

No. Targets cannot be added from your side. Our team registers each one to your organization, and a test can only point at a registered target.

All traffic to the platform is encrypted in transit. The measurements recorded during each run are kept for your package's retention period: 30, 180, or 365 days.

Berlin and Istanbul. Test origins include Frankfurt, Singapore, São Paulo, Tokyo, and more.