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
Side by side
7d window · 2.4 days observed · generated 2026-08-27 06:34:22 UTC
| Metric | PublicNode | Tenderly | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 94.8 | 77.9 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.97% | 99.89% |
| p50 latency | 18.2 ms | 19.8 ms | 118.5 ms |
| p95 latency | 33.5 ms | 62.0 ms | 209.2 ms |
| p99 latency | 69.6 ms | 834.2 ms | 232.7 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 2 |
| Unsupported | 0 | 0 | 0 |
| Samples | 94,540 | 93,824 | 93,652 |
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
+4.5points
- Latency+4.5
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.5points
- Latency+21.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.