rpc cluster: 60s cadence + 1RPC descope (per-IP budget fairness) - #981
Merged
Conversation
…ess budgets saturated by aggregate probe load)
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.
Problème
Les 3 IPs de probe saturaient les budgets keyless PAR IP: 1RPC ~1% de succès sur 16 chains (cap journalier/IP crevé x4.6 depuis l'expansion long-tail du 07-03), dRPC 55-80% (throttling CU keyless). On publiait notre propre empreinte comme "fiabilité" des providers.
Fix
Post-merge
Redeploy 3 régions Railway + purge de la fenêtre de fiabilité polluée (07-07 14:05 -> now) pour drpc/1rpc, précédent CoinStats/anti-cache.