Repository navigation
two endpoints went paid or rate-limited (cherry-pick of #2947) - #2948
Closed
Flotapponnier wants to merge 2 commits into
Closed
Flotapponnier wants to merge 2 commits into
Flotapponnier wants to merge 2 commits into
Conversation
… 0 ms Nodies has moved behind a paid plan on two of the six chains we probe it on. polygon-pokt.nodies.app and bsc-pokt.nodies.app both answer HTTP 403 with "The network of this endpoint requires a paid subscription plan", on every call from all three regions. We kept sending 4,320 calls per chain per 24h into that, and every one of them was classified http_err. The user-visible part is worse than the waste: a provider with no successful call publishes p50 0, and the Polygon page was showing a row reading 0 ms, which a reader takes as instant rather than as never answered. The other four Nodies endpoints (ethereum, arbitrum, optimism, base) still answer and are untouched. dRPC on BNB goes for a different reason. bsc.drpc.org rate-limits the probe cadence: 0 of 10 live tries, every one returning "You reached Public endpoint rate limit", and 3,018 http_err against 1,300 ok over 24h. Its published 64.3 ms was computed from the 30 percent of calls that got through, so it ranked above Binance on a number its own failure rate does not support. This is the same situation that already removed 1RPC from Oasis Sapphire. dRPC is healthy on every other chain in the cluster, Polygon included at 100 percent, and stays in all of those cohorts. BNB does not lose a row for it. bloXroute was already being probed at 100 percent and 9.9 ms in eu-west, fourth fastest on the chain and ahead of Binance, and simply was not in the spec. It is published now, so BNB keeps four providers, all at 99.98 percent or better. Polygon lands on three, all at 100 percent. Every keyless candidate was probed before settling for that: polygon-rpc.com, the chain's own endpoint, is now key-gated; blockpi returns 521; blastapi returns a JSON-RPC error; llamarpc and blxrbdn have no DNS for Polygon; ankr requires a key. Only 1RPC answered, 4 of 5, and 1RPC has twice been removed from this cluster for not sustaining continuous probing, so three providers at 100 percent is the better page. blastapi stays probed but unpublished on BNB. It answers at 97.94 percent but at 295.8 ms, far behind everything else, and it carries no logo or registry entry. It is available as a fifth row if the chain ever needs one.
) #2947 took dRPC and Nodies out of the BNB cohort, but the intro paragraph still read "PublicNode, dRPC and Nodies bring multi-chain coverage". The table was correct and the prose above it was not, which is the worse of the two failure modes because a reader trusts the sentence. Names the cohort as it stands, PublicNode, NOWNodes and bloXroute, and drops the claim about latency trending from EU origins rather than restating it for a different set of providers. No hardcoded leader: which one is fastest stays with the live data.
Collaborator
Author
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.
Cherry-pick of #2947, already merged to dev.
The spec half of that change is already live, because the materialize worker
reads specs from
dev, so the Polygon page has stopped publishing a 0 ms row.This merge is what stops the probing itself: the Railway rpc-capabilities
services deploy from
main, so until this lands we keep sending 4,320 callsper chain per 24h to two endpoints that answer HTTP 403 or rate-limit every one
of them.
Gates on this branch: go build, go vet, pnpm validate (245 specs), plus a check
that every URL each spec publishes is the URL the harness probes.