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
6h window · 6.0 hours observed · generated 2026-08-27 09:13:19 UTC
| Metric | PublicNode | Tenderly | MEV Blocker |
|---|---|---|---|
| Rank | 1 | 2 | 7 |
| Score | 99.4 | 99.0 | 69.4 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.99% | 99.98% | 99.91% |
| p50 latency | 19.1 ms | 18.5 ms | 119.6 ms |
| p95 latency | 31.7 ms | 32.8 ms | 208.4 ms |
| p99 latency | 66.8 ms | 105.5 ms | 227.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 1 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,521 | 8,444 | 8,440 |
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.4points
- Latency+0.4
- Availability+0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +0.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+30.0points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +30.0, exactly — the score is a weighted sum, so it comes apart.