Hit this today while verifying a batch of Ethereum addresses for puzzle research: fired 6 explorers_balance calls at once, 4 came back fine, 2 died with "Rate limited by etherscan". Retried those two manually with provider: blockscout and they answered immediately, so coverage was never the problem, the router just doesn't retry elsewhere.
Same family as #11 (BSC free-plan fallback), different trigger: there the plan can't serve the chain at all, here the provider works fine until you breathe on it in parallel. Proposal: on a rate-limit class error, retry once on another registered provider supporting the chain before surfacing the error. Would have saved the manual roundtrip.
Hit this today while verifying a batch of Ethereum addresses for puzzle research: fired 6
explorers_balancecalls at once, 4 came back fine, 2 died with "Rate limited by etherscan". Retried those two manually withprovider: blockscoutand they answered immediately, so coverage was never the problem, the router just doesn't retry elsewhere.Same family as #11 (BSC free-plan fallback), different trigger: there the plan can't serve the chain at all, here the provider works fine until you breathe on it in parallel. Proposal: on a rate-limit class error, retry once on another registered provider supporting the chain before surfacing the error. Would have saved the manual roundtrip.