Skip to content

fix: raise default GET /contents burst rate limit to 1000/min - #1978

Merged
pentreathm merged 1 commit into
mainfrom
fix/1977-raise-content-get-rate-limit
Oct 21, 2026
Merged

pentreathm merged 1 commit into
mainfrom
fix/1977-raise-content-get-rate-limit

Conversation

@decentraland-bot

Copy link
Copy Markdown
Collaborator

Summary

  • Raises DEFAULT_CONTENT_GET_RATE_LIMIT_MAX for GET/HEAD /contents/:hashId from 300 to 1000 requests per 60 s window.
  • Hourly (3,000) and daily (20,000) quotas are unchanged, so sustained crawlers like the 2026-10-04 incident stay bounded. Still overridable via CONTENT_GET_RATE_LIMIT_MAX.

Why

A 24h look at 429s across the peer* hosts (Cloudflare sampled data, Oct 20-21) showed regular residential/mobile-ISP browsers bursting to ~400-1,000 content requests in one minute during scene loads, and being rejected by the origin limiter (including the peer-ap1 CatalystContentRateLimited alert). Bulk curl/node-fetch scripts were far above that (~1.9k-8k req/min).

Testing

  • yarn build, yarn lint:check pass
  • jest test/unit: 71 suites, 760 tests pass

Note: nodes that set CONTENT_GET_RATE_LIMIT_MAX explicitly keep their override.

Closes #1977

Requested by Matias Pentreath via Slack

🤖 Generated with Claude Code

Residential clients burst to ~400-1,000 content requests per minute when
loading scenes and were rejected at the 300/min default. Hourly and daily
quotas are unchanged, so sustained crawlers remain bounded.

Closes #1977

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@pentreathm
pentreathm merged commit ab7290e into main Oct 21, 2026
4 checks passed
@pentreathm
pentreathm deleted the fix/1977-raise-content-get-rate-limit branch October 21, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Raise default GET /contents per-IP burst rate limit

2 participants