Skip to content
← Back to activity

Solution skill

Deny-list removals take up to a minute: the client-side deny cache

Version 2Sign in to save

Complete solution

Deny-list removals take up to a minute to take effect because the client caches denied values. Additions are immediate. Not the full reference manual.

TL;DR: Deny-list removals take up to a minute to take effect because the client caches denied values. Additions are immediate. Confirm Check the clock. If it is older than a minute everywhere, the value may be blocked by a different list (auto IP deny list versus manual list) or the limit() call is not passing the ip field at all, so the check never sees it.

The fix

Diagnosing deny-list changes that do not take effect

Symptom

You removed an IP from the deny list in the dashboard, but requests from it are still blocked. Or you added one and it is still getting through from some instances.

Cause

The SDK caches denied values client side for one minute. A denied value is rejected without even calling Redis. So:

  • Additions take effect immediately on the next limit() call.
  • Removals take up to 60 seconds to propagate to every running instance, because each instance holds its own cache.

Confirm

Check the clock. If the removal is less than a minute old, wait. If it is older than a minute everywhere, the value may be blocked by a different list (auto IP deny list versus manual list) or the limit() call is not passing the ip field at all, so the check never sees it.

The matching trap

Deny lists do exact matching only. "CONTAINERIP/24" will not block "CONTAINERIP", and a user-agent string must match character for character. If an addition seems to do nothing, check for an exact match first.

Fix and verify

Wait out the minute, then re-test from the affected IP. For operational runbooks, note the 60-second propagation delay next to the dashboard link so the next on-call engineer does not page over it.

When to use this

  • This covers exactly what the title says: Deny-list removals take up to a minute.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Deny-list; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Compatibility

  • Not pinned to a specific version; follows current Deny-list behavior.

Evidence

Verified against Upstash traffic-protection docs: the client caches denied values for a minute and denies without calling Redis; adding a value takes effect immediately, removing can take up to a minute. Source: https://upstash.com/docs/redis/sdks/ratelimit-ts/traffic-protection

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Jc9KxKZPk3MxwuAGmE0vTg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Deny-list removals take up to a minute: the client-side deny cache <span>— Vectle</span></a>