BNB Smart Chain method
web3_clientVersion
Returns the node software and version behind an endpoint.
How each provider handles it
| Provider | Status | Success | Median |
|---|---|---|---|
| NodeReal | Supported | 100.0% | 19 ms |
| BNB Chain | Supported | 100.0% | 18 ms |
| PublicNode | Supported | 99.9% | 23 ms |
| Blast API | Supported | 99.2% | 104 ms |
| 1RPConerpc | Rate limited | 1.1% | 1548 ms |
Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.
Over time
Median latency per day. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.
Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it.
When it degraded
A degradation is a bucket where a provider fell away from ITS OWN median for this method over the window, not from the cohort's. A provider that is consistently slower than its peers is not degraded — it is slower, which the ranking already says. Buckets with fewer than 20 samples are skipped, because a claim about a provider cannot rest on a handful of calls, and adjacent bad buckets are merged so one outage reads as one incident.
1RPC
median rose to 4253ms from a typical 742ms
latency · 2026-09-10 00:00Z
median rose to 2137ms from a typical 742ms
latency · 2026-09-13 00:00Z → 2026-09-14 00:00Z
median rose to 3428ms from a typical 742ms
latency · 2026-09-19 00:00Z → 2026-09-21 00:00Z
median rose to 2322ms from a typical 742ms
latency · 2026-09-25 00:00Z → 2026-09-26 00:00Z
median rose to 2364ms from a typical 742ms
latency · 2026-09-29 00:00Z
median rose to 1841ms from a typical 742ms
latency · 2026-10-01 00:00Z → 2026-10-02 00:00Z
median rose to 3629ms from a typical 742ms
latency · 2026-10-06 00:00Z → 2026-10-07 00:00Z
What it does
A free-form string such as `Geth/v1.14.11-stable/linux-amd64/go1.22.9`. It reveals which client implementation is serving requests.
Many commercial providers replace it with their own product name, which is a legitimate choice and means the field cannot be relied on to identify software.
Returns
String — the client version.
Try it
Runnable as written, against a keyless public endpoint. Nothing here needs an API key.
Request
curl -s https://ethereum-rpc.publicnode.com \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}'As JSON-RPC
{
"jsonrpc": "2.0",
"method": "web3_clientVersion",
"params": [],
"id": 67
}Response
{
"id": 67,
"jsonrpc": "2.0",
"result": "Geth/v1.14.11-stable/linux-amd64/go1.22.9"
}Things that bite
- Client diversity matters for the health of the network, but this string is not evidence of it: a proxy can return anything.
Why it is measured
It shows which providers run a stock client and which sit behind their own infrastructure, which frames the rest of their results.
Called every 900 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.
30d window · generated 2026-10-08 18:19:03 UTC · 5 providers