docs(nodes): reference OpenChainBench for live public RPC latency#2215
Open
Flotapponnier wants to merge 1 commit into
Open
docs(nodes): reference OpenChainBench for live public RPC latency#2215Flotapponnier wants to merge 1 commit into
Flotapponnier wants to merge 1 commit into
Conversation
Flotapponnier
requested review from
karlb and
seolaoh
and removed request for
a team
July 13, 2026 22:38
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.
Summary
Adds a one-line reference to OpenChainBench — Celo RPC at the end of the Community RPC Node discovery list in
tooling/nodes/overview.mdx, so developers picking a public endpoint can see live third-party latency comparisons.Why
The existing discovery list already includes third-party tools (Vido, Celo Community RPC Gateway, Stakely). OpenChainBench probes public no-key Celo endpoints from three regions every minute and publishes p50/p95/p99 latency, providing the same discovery utility with a live latency dimension.
Happy to reword or move if this doesn't fit the docs' tone.
Test plan