LOCAL SIMULATION · NO REAL SERVERS TOUCHED

Everything works.
Until it doesn’t.

Break simulated infrastructure. Watch requests fail. Discover what keeps the internet running.

Try it first: · ·

PREVIEW · REQUEST FLOW LIVE

Packets travel browser → DNS → server → database — until something breaks.

Simulation workspace

Every number below comes from the simulation engine — not random decoration. Simulated, not real, infrastructure.

● RUNNING SIM TIME T+00:00

Request rate every 1,600 ms

Traffic mix

Queue limit 12

Downloads a text summary of this session.

Total Requests0completed + in flight

Successful0returned a response

Failed0error or timeout

Success Rate—success ÷ completed

Avg. Latency—mean of completed reqs

Queue Depth0limit 12 · warn at 8

Active Failures0none

Cache Hit Rate—0 hits · 0 misses

Success rate history (last 24 completed requests)

Infrastructure map

Select a component to learn what it does. Cyan = request, lime = response, red = failed leg.

Request Response Failed

* Simulated resolver address, not a real lookup. Queue badge on the primary server shows requests waiting under overload. Click any node for its explainer.

SERVER QUEUE

0 / 12

LAST REQUEST No completed request yet.

Failure controls

Each button changes the real simulation state.

DNS Failure

OFF

New requests cannot resolve the server address.

Database Failure

OFF

Database-dependent requests fail. Cached and static content can survive.

Server Overload

OFF

Traffic arrives faster than the server can process it. The queue grows, latency rises, then timeouts start.

Primary Server Failure

OFF

The primary server goes down. Without a backup, its traffic fails.

Backup Server

STANDBY

When enabled and the primary fails, eligible traffic reroutes to the backup. It cannot bypass a DNS failure.

Cache Behaviour

When on, eligible cached responses are served without a fresh database query.

Attack Lab

Simulated attacks only. No real targets, no real traffic.

Attacks blocked: 0 · Attacks that hit: 0

DDoS Flood

OFF

A simulated botnet floods the primary server. Legitimate requests queue and time out unless rate limiting drops the flood.

DNS Spoofing

OFF

Fake DNS answers divert requests to the fake server. DNSSEC validation rejects the fake answers.

SQL Injection Attempt

OFF

Malicious database requests probe the database. A WAF blocks them; without it, the database degrades until the attack stops and it is restored.

Simulation only. Nothing here contacts a real server, DNS service, or website.

Component uptime since simulation start · updated every second

Browser

—

DNS

—

Primary

—

Backup

—

Database

—

Cache

—

Uptime counts seconds a component was healthy while the simulation was running. Overload counts as degraded for the primary; a disabled cache counts as down. The backup has no failure mode in this model, so it stays at 100%.

Event timeline

Real simulation events, newest first. Kept to the last 60.

No events yet. Press Launch Simulation, or wait for the first request — it appears here.

What just happened?

Select a component or trigger a failure to learn from it.

Normal operation

What happened: Requests flow browser → DNS → server → database or cache, then a response returns.

Why: Each step depends on the previous one. DNS answers “where is this site?”, the server runs the application, and the database or cache supplies the data.

What you observed: Cyan packets out, lime packets back, and the success rate holding near 100%.

How it recovers: Nothing to recover — this is the baseline every other scenario is compared against.

What this does not model: Real networks, TLS, CDNs, load balancers, or a real database. Latency here is simulated, in milliseconds, from queue depth — not measured from a live server.

DNS: Translates a name into an address.
Failover: Switching to the backup when the primary fails.
Cache hit: Served from stored data, no fresh query.
Latency: Simulated request-to-response time.