Skip to content

docs: link OpenChainBench public Injective RPC latency benchmark #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Flotapponnier wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: link OpenChainBench public Injective RPC latency benchmark #182

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .gitbook/infra/public-endpoints.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,3 +54,9 @@ For more EVM network details including Chain ID, contracts, and additional provi
| Explorer | https://testnet.explorer.injective.network/ |
| Faucet | https://testnet.faucet.injective.network/ |
| Status | https://uptime.com/statuspage/testnet.status.injective.network |

## Public latency benchmarks

For integrators comparing public Injective RPC providers, [OpenChainBench](https://openchainbench.com/benchmarks/injective-rpc) publishes a continuous latency benchmark of the Tendermint `status` method across the Injective Foundation endpoint and community providers (PublicNode, Polkachu, LavenderFive). Probes run every 60s from Paris, Virginia, and Singapore.

@coderabbitai coderabbitai Bot Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Correct the European probe location.

The benchmark methodology identifies the three regions as Virginia, Amsterdam, and Singapore; this sentence incorrectly says Paris. Please replace Paris with Amsterdam or use the canonical labels us-east, eu-west, and sgp. (openchainbench.com)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.gitbook/infra/public-endpoints.mdx at line 60, Update the OpenChainBench
probe-region description in the public Injective RPC provider section to replace
“Paris” with “Amsterdam,” preserving Virginia and Singapore.

Source: MCP tools


Source and methodology: [github.com/ChainBench/openchainbench](https://github.com/ChainBench/openchainbench).