What counts against my rate limit?

Each region a check runs from costs one token. A check across 10 regions costs 10 tokens.

I got a 429 — what now?

Wait for the number of seconds in the Retry-After header. The bucket refills continuously, so capacity returns on its own.

Rate limits & quotas

RegionCheck meters usage with a token bucket. Each region a check runs from costs one token; your plan sets the bucket size and refill rate.

How the bucket works

Every workspace (and every anonymous IP address) has a token bucket with a fixed capacity that refills continuously at a per-second rate. Running a check spends one token for each region it runs from — a check across 10 regions costs 10 tokens, all at once.

If you're not signed in, RegionCheck tracks your bucket by IP address. Signed-in usage is limited by your account and plan.

Daily caps

Some plans also apply an optional daily cap on top of the token bucket — a rolling 24-hour limit on total usage, independent of how quickly the bucket refills. This keeps a single burst-heavy day from being reachable purely by waiting for the bucket to refill.

When you're limited

When you're over a limit, RegionCheck responds with HTTP 429 and a Retry-After header telling you how long to wait. The response also identifies which kind of limit you hit:

burst — the token bucket is empty. It refills continuously, so retrying after the Retry-After window succeeds.
daily — the rolling 24-hour cap has been reached. Capacity returns as the window rolls forward.

Higher limits

Paid plans raise both the token bucket's capacity and refill rate, and increase how many regions a single check or scheduled check can use. See Plans & billing for what each plan includes.

Frequently asked questions

What counts against my rate limit?: Each region a check runs from costs one token. A check across 10 regions costs 10 tokens.
I got a 429 — what now?: Wait for the number of seconds in the Retry-After header. The bucket refills continuously, so capacity returns on its own.