rpc-capabilities: drop thirdweb from 8 chains (Railway IPs rate-limited) - #1292
Merged
Conversation
thirdweb rate-limits Railway shared IPs — sustained 95-100% probe failure on arbitrum/avalanche/base per 24h of alertmanager pages, and the same is observed on the other 5 chains where thirdweb was configured (ethereum/polygon/optimism/base/bnb/linea). Direct probes from other IPs succeed on all 8 endpoints (verified from Mac). Rate-limit is provider-side and IP-based; not a real availability signal. Drop thirdweb entirely from the free-tier bench. Coverage impact: ethereum 12 -> 11 polygon 5 -> 4 arbitrum 9 -> 8 optimism 6 -> 5 base 8 -> 7 bnb 7 -> 6 avalanche 5 -> 4 linea 4 -> 3 All chains keep >=3 providers; leaderboards stay credible. If we want thirdweb data back, route through rpc-keyed-latency with a paid client-id (env RPC_KEYED_URL_THIRDWEB_*).
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
1 participant
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.
thirdweb rate-limits Railway shared IPs. Alertmanager fires 95-100% probe failure sustained 24h. Direct hits from other IPs succeed (verified). Not a real availability signal.
Drop from ethereum/polygon/arbitrum/optimism/base/bnb/avalanche/linea. Each chain keeps >=3 providers.
If thirdweb data wanted back later: route through
rpc-keyed-latencywith a paid client-id (envRPC_KEYED_URL_THIRDWEB_*).