From 095005c4d8bd48a43647b35c3e8b6447608e679a Mon Sep 17 00:00:00 2001
From: Florent Tapponnier <160007691+Flotapponnier@users.noreply.github.com>
Date: Fri, 24 Jul 2026 15:55:37 +0200
Subject: [PATCH] docs: link OpenChainBench public Kaia RPC latency benchmark

---
 docs/references/public-en.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/references/public-en.md b/docs/references/public-en.md
index 06bc41605a32..1bc0f4051685 100644
--- a/docs/references/public-en.md
+++ b/docs/references/public-en.md
@@ -12,6 +12,10 @@ Hence, the main benefit of using an existing Public EN is that it allows you to
 - If traffic is concentrated on certain nodes, you may experience service delay.
 - To prevent too many requests, rate limits may apply on a per-node basis, which are subject to change without prior notification.
 
+## Public Latency Benchmarks
+
+For a neutral cross-check of the public endpoints listed below, [OpenChainBench](https://openchainbench.com/benchmarks/kaia-rpc) publishes continuous latency measurements for Kaia's keyless JSON-RPC providers. Probes run every 60 seconds from three regions (Paris, Virginia, Singapore) against `eth_getBlockByNumber`, and the harness is open source at [github.com/ChainBench/openchainbench](https://github.com/ChainBench/openchainbench).
+
 ## Public JSON-RPC Endpoints
 
 Below is the list of the network domains offered by Kaia’s Public Node Providers.