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 21:05:00 UTC
| Metric | Tenderly | PublicNode | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 94.3 | 70.8 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 19.3 ms | 25.2 ms | 110.1 ms |
| p95 latency | 32.8 ms | 53.0 ms | 191.2 ms |
| p99 latency | 58.0 ms | 113.5 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.47 blocks | 0.62 blocks |
| Rate limited | 0 | 0 | 1,308 |
| Unsupported | 0 | 0 | 12 |
| Samples | 8,235 | 8,307 | 1,949 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+5.1points
- Latency+5.2
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.1, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.5
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.