Version 3 of the shared rate limiter refuses a request when its Redis counter times out, instead of letting it through. It was published on Oct 28, 2026 and merged into every app that uses it the same day, with no opt-outs. Adopting it surfaced two bugs the old fail-open behaviour had been quietly covering.
A limiter exists for the moment someone is hammering a route. That is also the moment the counter store is most likely to be slow. If a slow store turns into a free pass, the limit disappears exactly when it is needed.
So the default flipped. A Redis timeout is now a refusal, and the caller decides what a refusal looks like for its own route. The change shipped together with a new major version of the shared feedback package, which builds on the same limiter, and patch releases raising the zod floor for a published advisory.
Making refusal possible meant reading every call site for what happens next. Two of them were wrong in ways that had never mattered before.
InvoiceUp's inbound receipts webhook answered 200 when the limiter timed out. That 200 told the sender the delivery was handled, and the receipt was dropped. It now answers 503, so the sender retries. In Hub, the intake form called `redirect()` inside a `try/catch {}`. The redirect threw, the empty catch swallowed it, and an over-limit submission was stored anyway. Both are fixed.
A refusal is only safe if every caller knows how to hear it.
Not all of them, on purpose. The dekimu.site lead form and the verify.dekimu.com playground mint had their own counters that failed open; both now refuse on their own timeouts. The status board's check endpoint refuses on a Redis timeout or error too, and it now keys on the last hop of the forwarded-for header, since the first hop is something a client can write.
Consent and DSA notices and plain read routes stay fail-open. Refusing a visitor's cookie choice or a page view because a counter was slow costs more than the abuse it would stop.
The package side is done. Limiters written before the shared package keep their own counters, and they are being brought onto the same rule one at a time rather than folded into this release. The remaining work is route-by-route judgement about what a refusal should say.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog