fix(243): scope every Robinhood Chain RPC claim to the Singapore probe

benchmarks/keyed-rpc-robinhood.yml

@@ -2,10 +2,10 @@
 
 slug: keyed-rpc-robinhood
 number: "243"
-title: "Fastest Robinhood Chain RPC with API key: Chainstack vs Alchemy vs QuickNode"
-seo_title: "Fastest Robinhood Chain RPC API key 2026: Chainstack vs Alchemy vs QuickNode latency"
-seo_description: "Live Robinhood Chain RPC latency: Chainstack, Alchemy, and QuickNode keyed endpoints probed every 60s. First public benchmark for this Arbitrum Orbit L2."
-subtitle: eth_getBlockByNumber latency against keyed Robinhood Chain endpoints (Chainstack, Alchemy, QuickNode), probed every 60 seconds.
+title: "Fastest Robinhood Chain RPC with API key, measured from Singapore: Chainstack vs Alchemy vs QuickNode"
+seo_title: "Fastest Robinhood Chain RPC API key 2026 from Singapore: Chainstack vs Alchemy vs QuickNode latency"
+seo_description: "Live Robinhood Chain RPC latency measured from Singapore: Chainstack, Alchemy, QuickNode keyed endpoints probed every 60s. Scoped to that probe origin."
+subtitle: eth_getBlockByNumber latency against keyed Robinhood Chain endpoints (Chainstack, Alchemy, QuickNode), probed every 60 seconds from Singapore. Every figure is scoped to that origin.
 category: RPCs
 status: live
 metric: RPC latency
@@ -18,21 +18,22 @@ seo_intro: |
   subsidy running through September 2026. It is a financially-sensitive
   chain with low tolerance for RPC latency.
   This bench probes Chainstack, Alchemy, and QuickNode on their keyed
-  Robinhood Chain endpoints every 60 seconds from Singapore, the closest probe region to the
-  chain’s Asia-Pacific infrastructure. Chainstack leads. This is the only independently-run public
+  Robinhood Chain endpoints every 60 seconds from Singapore. Chainstack posts the lowest median
+  from that origin. Round-trip latency depends on where the probe sits relative to each provider's
+  serving node, so this ranking is scoped to the Singapore probe and is not a chain-wide claim.
+  This is the only independently-run public
   latency benchmark for Robinhood Chain.
 
 abstract: |
   We measure the round-trip latency of eth_getBlockByNumber against the
   keyed endpoints of Chainstack, Alchemy, and QuickNode on Robinhood Chain.
   The probe uses a rotating JSON-RPC id to defeat edge caches, fires every
-  60 seconds from Singapore, the closest probe region to the chain's
-  Asia-Pacific infrastructure, and classifies each response as ok,
+  60 seconds from Singapore, and classifies each response as ok,
   http_err, jsonrpc_err, stale, or timeout. Only ok responses contribute to
   the latency distribution.
 
 methodology:
-  - "Cadence: every 60 seconds per provider from Singapore. Robinhood Chain runs on the Arbitrum Orbit stack with ~100ms block times; the 60s probe cadence captures 600 blocks per hour."
+  - "Cadence: every 60 seconds per provider from Singapore. Every figure on this page is scoped to that origin; provider ranking is origin-dependent. Robinhood Chain runs on the Arbitrum Orbit stack with ~100ms block times; the 60s probe cadence captures 600 blocks per hour."
   - "Payload: eth_getBlockByNumber('latest', false) with a rotating JSON-RPC id. Non-cacheable by design: the rotating id defeats body-keyed edge caches and forces the provider to serve a real Robinhood Chain tip."
   - "Authentication: Chainstack Global Node key (node-scoped, dedicated to Robinhood Chain; key in Railway env, not in repo). Alchemy uses its standard multi-chain key. QuickNode uses its shared-endpoint key for Robinhood Chain. All keys in Railway env, not in repo."
   - "Call-result classification: ok (HTTP 200 with usable block number), http_err, jsonrpc_err (HTTP 200 with error body), stale (block more than 20 behind the cross-provider tip), timeout. Latency is recorded only for ok responses."
@@ -52,13 +53,13 @@ aggregate_filters:
 
 faq:
   - q: "Which Robinhood Chain RPC provider is fastest?"
-    a: "Per the live data above: {{name:chainstack}} at {{p50:chainstack}} p50 (24h). It is the lowest-latency keyed provider for Robinhood Chain in this benchmark."
+    a: "From the Singapore probe: {{name:chainstack}} at {{p50:chainstack}} p50 (24h), the lowest-latency keyed provider for Robinhood Chain as measured from that origin."
   - q: "What is Robinhood Chain?"
     a: "Robinhood Chain (chain ID 4663) is an Arbitrum Orbit L2 built by Robinhood for tokenized equity trading. It launched on mainnet in July 2026 with ~100ms block times and a gas fee subsidy running through September 29, 2026. It supports EVM-compatible tooling and standard eth_ JSON-RPC methods."
   - q: "Why is this the only Robinhood Chain latency benchmark?"
     a: "Robinhood Chain is a new chain. OpenChainBench added it within days of Chainstack, Alchemy, and QuickNode support going live, making this the first and so far only independent latency measurement. Infura and Ankr do not currently list Robinhood Chain in their supported networks."
   - q: "Where does this benchmark probe from?"
-    a: "The probe runs from Singapore, the region closest to the chain’s Asia-Pacific infrastructure, where all three providers serve their lowest-latency responses. Additional probe regions may be added as the chain matures."
+    a: "From Singapore. Round-trip latency to a keyed RPC depends on where the probe sits relative to the provider's serving node, so every figure on this page is scoped to that origin: read it as fastest from Singapore, not fastest everywhere. Additional probe regions may be added as the chain matures."
 
 source: https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-keyed-latency
 

src/content/reports/rpc/2026-08-fastest-robinhood-chain-rpc.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Best Robinhood Chain RPC in 2026: Chainstack vs Alchemy vs QuickNode"
+title: "Best Robinhood Chain RPC in 2026, measured from Singapore: Chainstack vs Alchemy vs QuickNode"
 category: "rpc"
 slug: "2026-08-fastest-robinhood-chain-rpc"
 publishedAt: "2026-09-04"
 period: "September 2026"
 summary: "Robinhood Chain is live, and three providers offer keyed endpoints for it. We benchmarked all three on the same call, the same cadence, over a rolling 24-hour window. Here is which one delivers the fastest median read."
-heroFinding: "Chainstack posts the lowest median latency on Robinhood Chain, roughly 3 ms p50 over 24 hours, the best of any keyed provider on the chain."
+heroFinding: "Chainstack posts the lowest median latency on Robinhood Chain, roughly 3 ms p50 over 24 hours, the lowest of the three keyed providers as measured from our Singapore probe."
 author: "OpenChainBench Research"
 readingTime: 6
 canonical: "https://openchainbench.com/reports/rpc/2026-08-fastest-robinhood-chain-rpc"
@@ -23,15 +23,15 @@ canonical: "https://openchainbench.com/reports/rpc/2026-08-fastest-robinhood-cha
 
 Every number here is a live query against the [OpenChainBench Prometheus](https://openchainbench.com/methodology). The harness sends each provider an `eth_getBlockByNumber("latest", false)` request every 60 seconds, with a rotating JSON-RPC id so no edge cache can serve a canned response. Each probe forces a real Robinhood Chain tip.
 
-Each response is classified as ok, http_err, jsonrpc_err, stale (block more than 20 behind the cross-provider tip), or timeout. Latency is recorded only for ok responses, and the figures below are the p50 over a rolling 24-hour window. Probes run from Singapore, the closest probe region to the chain's Asia-Pacific infrastructure; that is the reference region for this bench.
+Each response is classified as ok, http_err, jsonrpc_err, stale (block more than 20 behind the cross-provider tip), or timeout. Latency is recorded only for ok responses, and the figures below are the p50 over a rolling 24-hour window. Probes run from Singapore, and every figure in this report is scoped to that origin. Round-trip latency to a keyed RPC depends on where the probe sits relative to the provider's serving node, so the ranking is origin-dependent.
 
 Live page, sparklines, and source: [keyed-rpc-robinhood](/benchmarks/keyed-rpc-robinhood).
 
 ## The Result: Chainstack Leads on Median Latency
 
 Three providers offer keyed Robinhood Chain endpoints today, and all three answer reliably. None dropped a probe over the window. So this is a clean speed comparison, and on the median the gap is wide.
 
-<Mark>Chainstack returns a Robinhood Chain block in roughly 3 ms at the median over 24 hours</Mark>, the lowest p50 of any keyed provider on the chain. Its Global Node sits closest to the chain's infrastructure and it shows in the round-trip.
+<Mark>Chainstack returns a Robinhood Chain block in roughly 3 ms at the median over 24 hours</Mark>, the lowest p50 of the three keyed providers from our Singapore probe. Its Robinhood Chain node answers that origin in single-digit milliseconds; the ranking is origin-dependent, and this report is scoped to Singapore.
 
 <StatTable bench="keyed-rpc-robinhood" caption="Keyed Robinhood Chain RPC providers, p50 latency over 24h. Lower is better." />
 
@@ -46,7 +46,7 @@ At ~3 ms median, Chainstack leaves the most headroom against that 100 ms cadence
 ## Which to Use
 
 <UseCase label="Latency-sensitive reads (quotes, head polling, trading UI)">
-Chainstack is the median leader in this cohort, roughly 3 ms p50 over 24h. If your priority is the fastest typical read on Robinhood Chain, it is the front-runner today. As with any single endpoint, pair it with a fallback so a provider-side incident never leaves you without a tip.
+Chainstack is the median leader in this cohort, roughly 3 ms p50 over 24h. If your priority is the fastest typical read on Robinhood Chain from Singapore, it is the front-runner today. As with any single endpoint, pair it with a fallback so a provider-side incident never leaves you without a tip.
 </UseCase>
 
 <UseCase label="Already standardized on Alchemy or QuickNode">