Every request picks a dimension. Two gateways spread traffic by latency and health, eject what breaks, keep each client inside its quota and decide releases with a sequential test. The traffic is simulated and starts when you open this page, but the failures are real.
reconnectingadmin
0 req/s0 failed0 429no data yet
Break a dimension
20 s, then it healsPick a dimension and a way to break it.
Portal fluid
20/s, burst 40, synced between both gatewaysYour own bucket on /fluid/. Fire 60 requests at once and watch where it runs dry. They all land on one gateway, and until the two gateways sync (every 100 ms) a client they haven't seen gets half the burst on each.
Canary
sequential test, at most 1% false rollbacksWaiting for the first snapshot.
The evidence shows up here once a rollout runs.
errors slow responses
What happened
Quiet so far.