You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: benchmarks/canto-rpc.yml
+18-87Lines changed: 18 additions & 87 deletions
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,8 @@ slug: canto-rpc
4
4
number: "146"
5
5
title: Fastest free Canto RPC, live no-key endpoint latency
6
6
seo_title: "Fastest free Canto RPC 2026"
7
-
seo_description: "{{best_name}} leads free Canto RPC at {{best_p50}} (eth_getBlockByNumber p50, 24h). 4 no-key providers measured every 60s from 3 regions."
8
-
subtitle: HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Canto RPC endpoint, audited every 60 seconds from 3 regions.
7
+
seo_description: "{{best_name}} leads free Canto RPC at {{best_p50}} (eth_getBlockByNumber p50, 24h). 1 no-key provider measured every 60s from 3 regions."
8
+
subtitle: HTTP round-trip latency for eth_getBlockByNumber against the free, no-key public Canto RPC endpoint, audited every 60 seconds from 3 regions.
9
9
10
10
category: RPCs
11
11
status: live
@@ -14,40 +14,40 @@ unit: ms
14
14
higher_is_better: false
15
15
16
16
seo_intro: |
17
-
Canto is a permissionless EVM L1 (chain 7700) built around free public infrastructure; its DEX, lending market, and stablecoin are protocol primitives rather than third-party dApps. The official endpoint (`canto.gravitychain.io`) is maintained by Plex, with dRPC, PublicNode, and Ankr providing additional keyless alternatives probed every 60 seconds from three regions.
17
+
Canto is a permissionless EVM L1 (chain 7700) built around free public infrastructure; its DEX, lending market, and stablecoin are protocol primitives rather than third-party dApps. The official endpoint (`canto.gravitychain.io`) is maintained by Plexand is the only keyless endpoint sustaining continuous probing from all three regions.
18
18
19
19
abstract: |
20
20
Per-chain member of the RPC latency cluster, extended to Canto.
21
21
We measure the round-trip latency of a single, identical RPC call
22
-
(`eth_getBlockByNumber`) against every no-key public Canto endpoint
23
-
that sustains continuous probing, 4 providers at launch,
24
-
every 60 seconds, from us-east, eu-west and Singapore. The harness
25
-
classifies every response (ok / http_err / jsonrpc_err / stale /
26
-
timeout) so the leaderboard rewards sustained availability rather than
27
-
fast error messages. The cross-chain view lives on the parent
28
-
`rpc-capabilities` benchmark; this page is the Canto-scoped answer
29
-
with per-region breakdowns as a first-class dimension.
22
+
(`eth_getBlockByNumber`) against the no-key public Canto endpoint
23
+
(Canto Official, canto.gravitychain.io), every 60 seconds, from
24
+
us-east, eu-west and Singapore. The harness classifies every response
25
+
(ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard
26
+
rewards sustained availability rather than fast error messages.
27
+
The cross-chain view lives on the parent `rpc-capabilities` benchmark;
28
+
this page is the Canto-scoped answer with per-region breakdowns
29
+
as a first-class dimension.
30
30
31
31
methodology:
32
32
- "Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs."
33
33
- "Payload: `{\"jsonrpc\":\"2.0\",\"id\":<rotating>,\"method\":\"eth_getBlockByNumber\",\"params\":[\"latest\",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request."
34
34
- "Latency: client-side round-trip delta in milliseconds, exposed as both a gauge and a histogram (buckets 50 ms → 10 s), so percentiles are computed via Prometheus `quantile_over_time` over the last 24 hours."
35
35
- "Call-result classification: `ok` (HTTP 200 + non-empty result), `http_err`, `jsonrpc_err` (HTTP 200 carrying an error body), `stale` (more than 20 blocks behind the cross-provider tip), `timeout`."
36
36
- "This page is part of the per-chain RPC cluster derived from the cross-chain [rpc-capabilities](https://openchainbench.com/benchmarks/rpc-capabilities) benchmark; the identical harness, cadence and exclusion rules apply on every chain."
37
-
- "Chain scope: every query on this page is pinned to `chain=\"canto\"`. Provider coverage at launch: 4 no-key endpoints (Canto Official, dRPC, PublicNode, Ankr)."
37
+
- "Chain scope: every query on this page is pinned to `chain=\"canto\"`. Provider coverage: 1 no-key endpoint (Canto Official). dRPC requires an API key; Ankr and PublicNode dropped free Canto support."
38
38
39
39
findings:
40
-
- "{{best_name}} currently leads free Canto RPC at {{best_p50}} (`eth_getBlockByNumber` p50, 24h) across 4 measured providers."
40
+
- "{{best_name}} currently leads free Canto RPC at {{best_p50}} (`eth_getBlockByNumber` p50, 24h)."
41
41
42
42
faq:
43
43
- q: "What is the fastest free Canto RPC right now?"
44
-
a: "{{best_name}} currently leads at {{best_p50}} (`eth_getBlockByNumber` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples."
44
+
a: "{{best_name}} currently leads at {{best_p50}} (`eth_getBlockByNumber` p50 over the last 24h), measured every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples."
45
45
- q: "Which Canto RPCs work without an API key?"
46
-
a: "4 endpoints sustain continuous keyless probing at launch: Canto Official, dRPC, PublicNode, Ankr. Every listed endpoint was live-verified before inclusion."
47
-
- q: "Does the fastest Canto RPC change by region?"
48
-
a: "Often. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate."
46
+
a: "The Canto Official endpoint (`canto.gravitychain.io`, operated by Plex) is the only keyless endpoint sustaining probes from all 3 regions. dRPC requires an API key; Ankr and PublicNode have dropped free Canto support."
47
+
- q: "Does the Canto RPC latency change by region?"
48
+
a: "Yes. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate."
49
49
- q: "How is Canto RPC latency measured here?"
50
-
a: "One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions. Responses are classified so an endpoint stuck on an old head or returning errors is never ranked as fastest."
50
+
a: "One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against the provider from each of 3 regions. Responses are classified so an endpoint stuck on an old head or returning errors is never ranked as fastest."
formula: "50th percentile over 24h of client-side round-trip latency (ms) for a single `eth_getBlockByNumber` POST sent every 60s from 3 regions (us-east + eu-west + sgp) to dRPC's no-key Canto endpoint."
tag: Allnodes-operated, 70+ chains, archive on most
117
-
formula: "50th percentile over 24h of client-side round-trip latency (ms) for a single `eth_getBlockByNumber` POST sent every 60s from 3 regions (us-east + eu-west + sgp) to PublicNode's no-key Canto endpoint."
formula: "50th percentile over 24h of client-side round-trip latency (ms) for a single `eth_getBlockByNumber` POST sent every 60s from 3 regions (us-east + eu-west + sgp) to Ankr's no-key Canto endpoint."
0 commit comments