The Rate Limit That Counted Everyone

Enterprise support says API 429s spike whenever a free-tier crawler runs. Limits are supposed to be per tenant. The counter key is only the route name.

Initial failing signaltenant B blocked by tenant A trafficExpected behavior: Traffic from tenant B is allowed independently of tenant A. · actual behavior: Tenant B receives HTTP 429 because tenant A consumed the shared limit.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Hit the limiter as tenant A until the bucket is full.
Hit the same route as tenant B.
Tenant B should still be allowed under its own budget.

Focus Mode

Start

src/limiter.js
src/gateway.js

Likely area

src/limiter.js
src/gateway.js
src/keys.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicReliability

DifficultyMedium

Est. time15 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace