Skip to content
Ddosphere

User guide

Run your first resilience test, end to end.

Ddosphere puts controlled, distributed load on infrastructure you own, so you can prove your mitigation before a real incident tests it. This guide walks through each screen in the order you meet it.

01

Sign in

Every account belongs to an organization, and your targets are registered to it by our team before your first run.

  1. 1Enter your work email and password to sign in.
  2. 2New here? Choose Create an account, add your name and email, and accept the Terms of Use and Privacy Policy.
  3. 3Open the confirmation email and follow the link to set your password.
  4. 4Forgot your password? Choose Forgot password and follow the link we send you.

02

Dashboard

The first screen after sign-in. It sums up your organization's runs, and it is where saved tests are started.

DRR Score
The average resilience rating across your runs, grouped by level.
By protocol
How many runs you have made, as a chart and a table, split by protocol.
Overview
Total runs, passes, failures, bandwidth, and test time so far.
Last ten runs
Response time and DRR Score for your ten most recent runs.
Run list
Every run with its level, layer, type, target, and status. Start, edit, or remove from here.

Filter the screen by label or by target to focus on one system.

03

Build a test plan

Choose New test, name it, and pick one of your registered targets. If a target is not listed yet, use Contact us and our team adds it.

  1. 1Set the duration, the regions the load comes from, and the level.
  2. 2Pick the test type and its volume. The product shows the volume unit and the ceiling for each level.
  3. 3Add the port, and a protocol where the type needs one.
  4. 4Add more steps to the plan if you want, each with its own type, load, and duration.
  5. 5Choose what happens between steps: continue automatically, or wait and then stop.
  6. 6Save the plan to start later, or start it now.

Open a saved plan again from the run list to change any of these settings.

04

Follow a run live

Starting a plan opens the live screen. You watch the run unfold and hold the emergency stop the whole time.

Origins and targets
The regions the load comes from, and the target it reaches.
Steps
Each step in the plan, with the time left until the next one.
World map
Origins and target drawn on the globe as the run moves.
Health
Average response time as the run goes on.
Volume
The load graph, in the unit that fits the type.
Emergency stop
Stop the whole run, or the current step, at any second.

05

Read the report

When a run ends, the report lays out what happened. Filter it to one test type, or read the average across the run.

Run details
Times, type, layer, protocol, port, regions, target, volume, and bandwidth.
Hits
Total, successful, and failed hits, with average response time.
DRR Score
How the target held, as a single resilience rating.
Graphs and logs
The volume graph, health status, and the run log, with your notes.

Export any report as a PDF your team can pass around.

06

Compare runs

Put two or three runs side by side to see whether a change moved the numbers.

  1. 1Pick two or three runs to compare.
  2. 2Choose the metrics you want to line up.
  3. 3Read them on one graph, or split the graph by metric.

Export the comparison as a PDF.

07

Schedule runs

Book a plan for later, once or on a repeat, and track it from the schedule list.

  1. 1Choose Add schedule and pick the plan.
  2. 2Set the day and time.
  3. 3For a one-off, save and schedule.
  4. 4For a repeat, set how often and until when, then save and schedule.

Every schedule you create shows up in the schedule list.

08

Account and team

Open account settings from your profile picture to manage your profile, team, plan, and notifications.

Account
Update your profile details and picture.
Company and team
See roles, add teammates, and set who can do what.
Plan
Your current plan, when it renews, and how it compares to the others.
Notifications
Choose what you are told about.

Admins and members with the Attacker role build and run tests. Observers follow runs and read results, and cannot change anything.

Still stuck?

Reach our team at [email protected] or through the contact form in the app.