Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 06:55:22 UTC
| Metric | PublicNode | Tenderly | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 98.9 | 70.1 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 100.00% | 100.00% |
| p50 latency | 17.8 ms | 18.6 ms | 105.0 ms |
| p95 latency | 30.6 ms | 32.2 ms | 192.8 ms |
| p99 latency | 55.1 ms | 64.6 ms | 268.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.47 blocks | 0.51 blocks |
| Rate limited | 0 | 0 | 1,489 |
| Unsupported | 0 | 0 | 19 |
| Samples | 9,669 | 9,581 | 2,114 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against PublicNode, the highest scorer of those selected.
PublicNodevsTenderly
+0.5points
- Latency+0.5
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +0.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.3points
- Latency+29.2
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +29.3, exactly — the score is a weighted sum, so it comes apart.