Skip to tool
Skip to tool
💻 Developer & Code
ECECH AppPrecision calculator

Calculate Exponential Backoff Delay

Sum the wait after each failed attempt, then include the time spent on every request.

Set the retry policy

Adjust the first wait, retry count, multiplier, and request duration. The schedule updates as you type.

Retries after the first request.

Estimated elapsed time

—

Retry waiting time

—

If first wait is 10% longer

—

Total requests

—

Retry wait schedule

Each interval grows by the selected multiplier.

    This estimate has no maximum-delay cap, random jitter, or server-provided Retry-After value. Real retry policies may include those rules.

    Advertisement

    How the retry delays add up

    For r retries, the wait is base × (1 + multiplier + … + multiplierr−1). The elapsed estimate adds one request duration for the initial call and each retry.

    Retry 11 sec
    Retry 22 sec
    Retry 34 sec
    Retry 48 sec
    Retry 516 sec
    Retry 632 sec

    The sample sums to 63 seconds of waiting. Retry count does not include the first request.

    How to use the exponential backoff calculator

    Set the initial wait, number of retries, multiplier, and request time. The schedule lists each delay; the main result adds all retry waits and the duration of the initial request plus every retry.

    What counts as a retry?

    The first request is attempt 1. The retry count is the number of additional requests after that initial attempt. Six retries therefore means seven total requests and six waits.

    Worked example: 1 second, 6 retries, multiplier 2

    The waits are 1 + 2 + 4 + 8 + 16 + 32 = 63 seconds. If each request takes 0.5 seconds, seven requests add 3.5 seconds, for 66.5 seconds elapsed under this simple model.

    Model limits

    This calculator applies the multiplier exactly as entered. It does not cap the maximum delay, add random jitter, apply a server-provided Retry-After value, or decide which errors are safe to retry. Those details vary by service and retry policy. For example, Google Cloud Storage documents configurable maximum retry times and delay values for particular client libraries. Confirm the actual policy in the system you operate.

    Sources & assumptions

    Verified 2026-10-28. The calculator uses a plain geometric retry schedule without caps or jitter; it is not a substitute for your service's configured policy.

    Official reference

    Advertisement

    Frequently Asked Questions

    How do I calculate total exponential backoff wait?
    Add the delay before each retry. With base 1 second, six retries, and multiplier 2, the waits are 1, 2, 4, 8, 16, and 32 seconds, totaling 63 seconds.
    Does retry count include the first request?
    No. Retry count means additional requests after the initial request. The total request count is retries plus one.
    Does this include request duration, jitter, or a maximum delay?
    You may enter a fixed duration for each request. The estimate does not include random jitter, a maximum-delay cap, or server-provided Retry-After values.
    Does any value leave my browser?
    No. The schedule and estimate are calculated locally in your browser; ecech does not receive the entered values.

    Related tools in Developer & Code

    Browse all Developer & Code tools
    The Mac mini the ecech. site is built on, beside a handwritten note reading ecech.com.

    Made by one person

    ecech. is not a content farm. Every tool here is written and checked by hand, one at a time, by someone who wanted the tool to exist and could not find a version that showed its working.

    No accounts and no sign-in, and nothing you type reaches a server — every calculation on this page runs inside your browser. The ads are served by Google and do set their own cookies, which is set out in full on the privacy page. More about the site.