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 Solana
Side by side
24h window · 24 hours observed · generated 2026-10-08 17:46:08 UTC
| Metric | PublicNode | Tatum |
|---|---|---|
| Rank | 1 | 3 |
| Score | 93.1 | 63.5 |
| Status | Excellent | Degraded |
| Availability | 99.39% | 99.33% |
| p50 latency | 24.4 ms | 27.3 ms |
| p95 latency | 48.3 ms | 93.4 ms |
| p99 latency | 134.4 ms | 194.8 ms |
| Correctness | 99.40% | 99.33% |
| Head lag | 8.58 blocks | 7.48 blocks |
| Rate limited | 0 | 930 |
| Unsupported | 164 | 0 |
| Samples | 44,145 | 13,245 |
3 providers scored against each other. A cohort this small makes every rank a comparison between very few alternatives: first of 3 is a weaker claim than the same score on a crowded chain, and the score is relative to whoever is here.
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.
PublicNodevsTatum
+29.5points
- Latency+30.0
- Head freshness−0.5
- Availability+0.0
- Correctness+0.0
The parts add to +29.5, exactly — the score is a weighted sum, so it comes apart.