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
24h window · 24 hours observed · generated 2026-08-28 01:07:15 UTC
| Metric | PublicNode | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 8 |
| Score | 97.7 | 86.6 | 83.8 | 58.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 99.97% | 75.93% |
| p50 latency | 21.8 ms | 87.4 ms | 106.3 ms | 1326.0 ms |
| p95 latency | 41.5 ms | 100.0 ms | 123.7 ms | 7406.7 ms |
| p99 latency | 98.6 ms | 128.6 ms | 151.1 ms | 9776.0 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 96.96% |
| Head lag | 0.48 blocks | 0.34 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 289 | 6,418 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 37,784 | 36,839 | 37,431 | 7,710 |
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.
PublicNodevsNodeReal
+11.1points
- Latency+11.2
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+13.9points
- Latency+14.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+28.3
- Availability+9.6
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.