Evidence / RPC measurements
Measure the request your app actually makes.
Latency depends on your location, chain, method and response size. This small sample shows a reproducible check of one public endpoint. It is not a claim about worldwide performance.
Ethereum · eth_blockNumber
- Measured
- 2026-09-28T18:30:46.335Z
- Samples
- 5
- Successful responses
- 5
- Errors / timeouts
- 0
- Median (p50)
- 112 ms
- p95 (small sample)
- 193 ms
NodeFlare control host; geographic location not independently verified. Small single-host sample, not global latency, throughput, historical uptime or an SLA.
Download the complete measurement →Reproduce the check
Five sequential requests, at least 11 seconds apart, no discarded warmup. Timing includes connection setup, network, gateway and the full JSON response. A response counts as successful only when HTTP and JSON-RPC succeed with a valid block number. Timeouts count as errors.
curl -sS --max-time 10 \
-w '\nHTTP %{http_code}; total %{time_total}s\n' \
https://rpc.nodeflare.app/eth/public \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Inspect the JSON result as well as the HTTP status. Do not load-test the public endpoint; use an agreed keyed workload for capacity tests.