docs: add RPC latency benchmark to Resources - #440
Open
Flotapponnier wants to merge 1 commit into
Open
Conversation
Flotapponnier
requested review from
Jonathansumner,
MissingNO57 and
pbukva
as code owners
August 29, 2026 15:22
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.
Adds an independent RPC latency benchmark link to the Resources section.
The benchmark continuously monitors public FetchHub-4 RPC endpoints, reporting p50/p90/p99 latency and availability from 3 global regions over 24h windows — useful for developers choosing a reliable endpoint.
No code changes, documentation only.