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:57:48 UTC
| Metric | PublicNode | Blast API | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 5 | 7 | 8 |
| Score | 98.8 | 83.7 | 76.7 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 99.91% | 79.94% |
| p50 latency | 20.0 ms | 104.6 ms | 121.5 ms | 1326.0 ms |
| p95 latency | 34.9 ms | 120.5 ms | 215.3 ms | 7406.7 ms |
| p99 latency | 74.4 ms | 148.2 ms | 231.5 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 99.97% | 96.96% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.38 blocks | 0.94 blocks |
| Rate limited | 0 | 36 | 0 | 1,634 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,746 | 9,657 | 9,651 | 2,221 |
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
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+22.1points
- Latency+22.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.5points
- Latency+29.3
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.5, exactly — the score is a weighted sum, so it comes apart.