Authorized Network Testing Only

IP Stresser &
IP Booter Platform

Stressthem is a high-capacity, low-latency stress testing platform engineered for penetration testers, network operators and security researchers. Push your infrastructure to its limits with controlled Layer 4 and Layer 7 attack vectors and find breaking points before attackers do.

0Tbps
Network Capacity
0
Attack Vectors
0
Uptime SLA
0
Avg. Boot Time
stressthem@console ~ live
$ stressthem boot --target stress-test.lab --method UDP-FLOOD --time 60 --port 80
[i] Authenticating API token... OK
[i] Resolving target → 203.0.113.42
[i] Allocating amplification nodes (16)... ready
[✓] Stress test launched · job #4827-a9c1
─────────────────────────────────────────
[~] Sending 64.2 Gbps sustained · pps 8.1M
[~] Sending 71.8 Gbps sustained · pps 9.4M
[✓] Test completed in 60s · target responsive
$
initializing live feed...
Authorized testing only · All launches are logged & verified
24/7 NOC · Global anycast network
L4 + L7 · 40+ vectors supported
3 Tbps aggregate capacity
Authorized testing only · All launches are logged & verified
24/7 NOC · Global anycast network
L4 + L7 · 40+ vectors supported
3 Tbps aggregate capacity
Why Stressthem

Built for professional stress testing

Whether you are validating a new deployment, hardening a production load balancer, or simulating adversarial traffic for a red-team engagement, Stressthem gives you the tooling, the bandwidth and the visibility to do it safely, repeatably and at scale.

Multi-Tbps Capacity

A globally distributed anycast network with more than 3 Tbps of dedicated stress-test capacity. Spin up a 100 Gbps flood in seconds and scale linearly without node warm-up, so your tests reflect what a real world-wide attack would actually look like.

Authorization Layer

Every target must be pre-authorized through DNS TXT verification, HTTP file challenge or signed ownership tokens. Unauthorized launches are blocked at the API gateway and reported to your account audit log for compliance traceability.

Live Telemetry

Real-time graphs for throughput (Gbps), packet rate (pps), target RTT and error ratios. Every job produces a downloadable HAR + PCAP-style capture so you can correlate client-side impact with infrastructure metrics in your own observability stack.

Layer 4 & Layer 7

Forty-plus vectors spanning transport-layer floods (UDP, TCP SYN/ACK, ICMP, amplification) and application-layer floods (HTTP GET/POST/HEAD, SLOWLORIS, slow body, cache bypass). Each method is documented with parameters, expected impact and detection signatures.

Developer API

A clean REST + WebSocket API lets you embed stress testing into CI/CD pipelines, chaos engineering workflows and on-call drills. SDKs available for Python, Go, Node.js and shell, with idempotent launches and signed webhooks for job completion.

12ms Boot Time

Pre-warmed amplification pools and anycast routing mean the time between an API call and the first packet leaving our edge averages just 12 milliseconds. No queues, no cold starts — ideal for time-boxed chaos drills and incident game-days.

Attack Surfaces

Layer 4 vs Layer 7

Modern infrastructure fails in two different places: at the network/transport layer where bandwidth and connection state are exhausted, and at the application layer where CPU, memory, sessions and databases are the bottleneck. Stressthem covers both, with distinct method families tuned for each.

Layer 4 · Transport

Network & Transport Floods

OSI Layer 3–4 · IP / TCP / UDP / ICMP

Layer 4 methods target the network and transport stack. They aim to saturate the victim's internet pipe, exhaust firewall state tables, consume connection-tracking memory or fill NAT sessions. These vectors are bandwidth-heavy and state-driven — they do not care what application is running on the target, only that packets can reach it. Amplification techniques use misconfigured third-party services to multiply outgoing traffic by factors of 50x to 50,000x.

  • UDP, TCP SYN, TCP ACK, ICMP floods
  • NTP, DNS, SSDP, CLDAP, Memcached amplification
  • Per-port, per-protocol and multi-vector mixing
  • Spoofed source IP support on eligible targets
  • Up to 100 Gbps per single job
Layer 7 · Application

Application-Layer Floods

OSI Layer 7 · HTTP / HTTPS / WebSocket

Layer 7 methods target the application itself. They mimic legitimate user behavior at the HTTP/HTTPS level, consuming server CPU by triggering expensive endpoints, exhausting PHP-FPM / Tomcat / Node worker pools, draining database connection pools or filling session stores. These vectors require very little bandwidth — a single laptop can produce a damaging L7 flood — but they are extremely hard to detect because the traffic looks superficially identical to real users.

  • HTTP GET / POST / HEAD / PUT floods
  • SLOWLORIS, slow body, slow read
  • Cache-bypass, range-header CPU exhaustion
  • Real-browser fingerprint & JS challenge solver
  • TLS handshake / HTTPS renegotiation floods
Explore full methods catalog
0
Dedicated stress capacity across the global anycast network
0
Distinct attack vectors across Layer 4 and Layer 7
0
Points of presence in North America, EU, Asia and LATAM
0
Average time from API call to first packet on the wire
Pricing

Plans that scale with your tests

Transparent monthly plans for individuals, teams and enterprise security programs. No hidden launch fees, no per-job surcharges — what you see is what you pay. All plans include the full method catalog, the developer API and audit-log export.

Starter
For individual researchers
$120/ mo
  • 10 Gbps per launch
  • 600 seconds max duration
  • 3 concurrent jobs
  • L4 + L7 methods
  • 5 authorized targets
  • API access
  • PCAP export
Choose Starter
Enterprise
For NOCs, MSSPs, large programs
$470/ mo
  • 200 Gbps per launch
  • Unlimited duration
  • Unlimited concurrent jobs
  • Custom amplification nodes
  • Unlimited authorized targets
  • Dedicated API rate limits
  • 24/7 priority NOC support
Contact Sales
FAQ

Frequently asked questions

Quick answers on legal use, supported methods, billing and integration. If something is missing, the documentation page has the long-form version with code samples.

Is using an IP stresser / IP booter legal?
Stress testing infrastructure that you own or have written authorization to test is legal in most jurisdictions and is considered a standard part of security engineering, chaos drills and capacity planning. Using a stresser against targets you do not own or do not have explicit permission to test is illegal in most countries and can carry criminal and civil penalties. Stressthem enforces authorization checks on every target and reserves the right to suspend accounts that bypass these checks.
How does Stressthem verify that I own a target?
Three verification methods are supported: a DNS TXT record containing a per-account token, an HTTP challenge file served from the root of the target domain, or a signed ownership token issued by your cloud provider (AWS, GCP, Azure, Cloudflare). Targets must be re-verified every 30 days. Verification is enforced at the API gateway — unverified targets cannot receive traffic, even from an authenticated account.
What is the difference between Layer 4 and Layer 7 methods?
Layer 4 methods operate at the transport layer (TCP, UDP, ICMP) and aim to saturate bandwidth, connection state or firewall tables — they do not need to understand the application. Layer 7 methods operate at the HTTP/HTTPS application layer and aim to exhaust application worker pools, database connections or session storage by mimicking real user requests. Layer 4 is bandwidth-driven; Layer 7 is request-driven. A complete stress test program exercises both.
Do you log and audit every launch?
Yes. Every API call, target verification, launch, parameter set and resulting traffic pattern is recorded to an immutable audit log retained for 18 months. Account owners can export their own audit trail as JSONL or CSV from the dashboard. This supports compliance frameworks such as SOC 2, ISO 27001 and PCI DSS penetration-testing evidence requirements.
Can I integrate Stressthem into CI/CD pipelines?
Yes. The REST API supports idempotent launches via a client-provided request ID, so a retried pipeline run will not double-launch. Official SDKs are available for Python, Go, Node.js and shell. A common pattern is to run a 60-second Layer 7 flood against a staging environment as part of the release gate, then assert that error-rate and p99 latency stay within SLO. Signed webhooks notify your pipeline when a job completes.
What payment methods do you accept?
Visa, Mastercard, American Express via Stripe; PayPal; bank transfer for annual Enterprise contracts; and selected cryptocurrencies (BTC, ETH, USDT, LTC, XMR) for privacy-conscious researchers. All billing is in USD. Annual plans receive a 20% discount versus monthly billing.

Ready to stress-test your infrastructure?

Create an account, verify your first target and launch your first stress test in under five minutes. No credit card required for the 24-hour trial.