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
- PublicNode
- Tenderly
- NodeReal
- dRPC
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 11:20:26 UTC
| Metric | PublicNode | Tenderly | Blast API | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 2 | 5 | 7 |
| Score | 99.4 | 99.4 | 78.3 | 69.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.99% | 99.98% | 99.95% |
| p50 latency | 20.6 ms | 18.7 ms | 105.0 ms | 121.6 ms |
| p95 latency | 32.7 ms | 32.8 ms | 119.6 ms | 206.6 ms |
| p99 latency | 63.8 ms | 59.5 ms | 131.5 ms | 225.2 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 99.99% |
| Head lag | 0.50 blocks | 0.48 blocks | 0.42 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 265 | 0 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,721 | 8,652 | 8,655 | 8,642 |
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.0points
- Latency+0.0
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV 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.