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
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 01:08:07 UTC
| Metric | PublicNode | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 6 | 8 |
| Score | 98.6 | 83.7 | 78.0 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% | 79.94% |
| p50 latency | 19.8 ms | 104.8 ms | 106.4 ms | 1326.0 ms |
| p95 latency | 35.5 ms | 120.8 ms | 192.9 ms | 7406.7 ms |
| p99 latency | 77.4 ms | 149.1 ms | 281.6 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.48 blocks | 0.94 blocks |
| Rate limited | 0 | 30 | 1,377 | 1,402 |
| Unsupported | 0 | 0 | 14 | 0 |
| Samples | 8,395 | 8,311 | 2,017 | 1,954 |
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.
PublicNodevsBlast API
+14.9points
- Latency+14.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.6points
- Latency+20.7
- Availability−0.0
- Correctness−0.0
- Head freshness−0.0
The parts add to +20.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.3points
- Latency+29.2
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.3, exactly — the score is a weighted sum, so it comes apart.