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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 23:29:02 UTC
| Metric | Tenderly | PublicNode | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 7 |
| Score | 99.4 | 96.2 | 70.8 | 69.5 |
| Status | Excellent | Excellent | Degraded | Degraded |
| Availability | 100.00% | 100.00% | 100.00% | 99.94% |
| p50 latency | 18.8 ms | 22.7 ms | 107.8 ms | 123.4 ms |
| p95 latency | 32.2 ms | 43.5 ms | 190.5 ms | 216.2 ms |
| p99 latency | 53.6 ms | 99.7 ms | 236.0 ms | 237.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 99.98% |
| Head lag | 0.47 blocks | 0.47 blocks | 0.52 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 1,417 | 0 |
| Unsupported | 0 | 0 | 16 | 0 |
| Samples | 8,883 | 8,969 | 2,123 | 8,881 |
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
+3.2points
- Latency+3.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +3.2, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMerkle
+28.6points
- Latency+28.6
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +28.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsMEV Blocker
+29.9points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +29.9, exactly — the score is a weighted sum, so it comes apart.