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
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 06:26:06 UTC
| Metric | PublicNode | Blast API | Merkle | MEV Blocker |
|---|---|---|---|---|
| Rank | 1 | 5 | 6 | 7 |
| Score | 99.4 | 78.4 | 70.1 | 69.5 |
| Status | Excellent | Good | Degraded | Degraded |
| Availability | 99.98% | 99.98% | 100.00% | 99.92% |
| p50 latency | 17.7 ms | 103.2 ms | 104.8 ms | 118.6 ms |
| p95 latency | 30.6 ms | 116.4 ms | 193.2 ms | 207.1 ms |
| p99 latency | 55.5 ms | 143.9 ms | 283.4 ms | 224.9 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.51 blocks | 0.41 blocks |
| Rate limited | 0 | 79 | 1,391 | 0 |
| Unsupported | 0 | 0 | 18 | 0 |
| Samples | 8,878 | 8,808 | 1,962 | 8,770 |
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
+21.1points
- Latency+21.1
- Head freshness−0.1
- Correctness+0.0
- Availability+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+29.3points
- Latency+29.3
- Head freshness+0.0
- Availability−0.0
- Correctness+0.0
The parts add to +29.3, 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.