Repository navigation
fix: raise default GET /contents burst rate limit to 1000/min - #1978
Merged
Merged
Conversation
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
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DEFAULT_CONTENT_GET_RATE_LIMIT_MAXforGET/HEAD /contents/:hashIdfrom 300 to 1000 requests per 60 s window.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-ap1CatalystContentRateLimitedalert). Bulkcurl/node-fetchscripts were far above that (~1.9k-8k req/min).Testing
yarn build,yarn lint:checkpassjest test/unit: 71 suites, 760 tests passNote: nodes that set
CONTENT_GET_RATE_LIMIT_MAXexplicitly keep their override.Closes #1977
Requested by Matias Pentreath via Slack
🤖 Generated with Claude Code