Rate Limit Increase Success Block for React

Nothing was changed or sent. The limits per endpoint and region and the burst buckets are typed sample data, and the benchmark only works a sample result out from the new limit (99 percent of it, held for 30 seconds, none refused). To wire it, fill ENDPOINTS with your before and after limits for each region and BURSTS from your bucket settings; the combined figures, the multiples, the bar widths and the sentences are worked out from them, and the all-regions scope is the sum of the regions.

They are a group of three buttons with one always on. Choosing a region re-derives the sentence, both meters, the three endpoint rows and the burst line from that region's numbers, says the multiple in the status line, and keeps the panel's height.

On one fixed axis, so a smaller region shows shorter bars: the hollow bar is the limit before and the filled bar is the limit now, and the words under each pair give both numbers. Nothing relies on the drawing, which is hidden from assistive technology; the sentence and each row say the same figures, and the key under the first meter names the two bars.

It says a sample benchmark is running, waits a moment while the button keeps its size and stays focusable, then reports a typed sample result for the chosen region: how many requests per second held for 30 seconds, and that none was refused. Nothing is sent. Connect it to your own load test and show its real result.

The bucket's size, how many requests it gains a second and how long an empty one takes to fill, which is the size divided by the refill rate (4 seconds in the EU, 6 in the US, 5 for all regions).

Run a benchmark is a Shine Button with a click handler that gives the local result, not a link. The handler is the framework's own click handler. Replace its body with a call to your load test.