Benchmarks

Provider incidents

An availability percentage has no shape. A provider that failed for twenty minutes and one that failed a request an hour all day can end the window with the same figure — this is the difference between them: when it started, how long it lasted, and which call it affected.

What happened

Runs where a provider departed from its own normal behaviour. A provider that always fails a given call is not having an incident when it fails it today — those are below, counted once each rather than repeated down this list.

Provider incidents, newest first
Started	What	Provider	Call	Lasted	Succeeded
2026-10-08 18:05	Throttled	Tatum	getBlockHeight	3m	0%vs 100%
2026-10-08 17:42	Throttled	Tatum	getBlockHeight	13m	0%vs 100%
2026-10-08 17:38	Throttled	Tatum	getSlot	6m	100%vs 98%
2026-10-08 16:38	Throttled	Tatum	getSlot	7m	100%vs 97%
2026-10-08 15:34	Throttled	Tatum	getBlockHeight	3m	0%vs 100%
2026-10-08 15:23	Throttled	Tatum	getHealth	8m	0%vs 100%
2026-10-08 15:04	Throttled	Tatum	getLatestBlockhash	8m	100%vs 99%
2026-10-08 15:01	Degraded	Tatum	getSlot	5m	75%vs 99%
2026-10-08 14:47	Throttled	Tatum	getLatestBlockhash	3m	100%vs 98%
2026-10-08 14:44	Degraded	Tatum	getSlot	6m	67%vs 97%
2026-10-08 13:53	Throttled	Tatum	getHealth	4m	0%vs 100%
2026-10-08 13:05	Throttled	Tatum	getLatestBlockhash	3m	100%vs 98%
2026-10-08 13:00	Throttled	Tatum	getLatestBlockhash	3m	100%vs 98%
2026-10-08 12:16	Throttled	Tatum	getLatestBlockhash	8m	100%vs 99%
2026-10-08 11:23	Throttled	Tatum	getSlot	12m	100%vs 99%
2026-10-08 10:59	Throttled	Tatum	getSlot	3m	67%vs 97%
2026-10-08 10:46	Throttled	Tatum	getSlot	3m	100%vs 99%
2026-10-08 09:20	Throttled	Tatum	getAccountInfo	20m	0%vs 100%
2026-10-08 09:18	Throttled	Tatum	getSlot	7m	50%vs 97%
2026-10-08 08:57	Throttled	Tatum	getHealth	9m	0%vs 100%
2026-10-08 08:37	Throttled	Tatum	getLatestBlockhash	4m	100%vs 98%
2026-10-08 08:37	Throttled	Tatum	getLatestBlockhash	3m	100%vs 98%
2026-10-08 08:37	Throttled	Tatum	getSlot	4m	100%vs 97%
2026-10-08 08:37	Throttled	Tatum	getSlot	9m	50%vs 99%
2026-10-08 08:14	Throttled	Tatum	getBlockHeight	3m	0%vs 100%
2026-10-08 07:46	Degraded	PublicNode	getLatestBlockhash	5m	50%vs 99%
2026-10-08 07:02	Degraded	Tatum	getLatestBlockhash	7m	67%vs 98%
2026-10-08 06:07	Degraded	Tatum	getSlot	9m	75%vs 99%
2026-10-08 06:06	Throttled	Tatum	getHealth	7m	0%vs 100%
2026-10-08 05:22	Degraded	Tatum	getLatestBlockhash	17m	75%vs 98%
2026-10-08 05:04	Throttled	Tatum	getSlot	3m	100%vs 99%
2026-10-08 04:37	Throttled	Tatum	getLatestBlockhash	10m	100%vs 99%
2026-10-08 04:27	Throttled	Tatum	getLatestBlockhash	5m	100%vs 98%
2026-10-08 03:24	Degraded	PublicNode	getLatestBlockhash	13m	50%vs 99%
2026-10-08 03:01	Throttled	Tatum	getHealth	6m	0%vs 100%
2026-10-08 02:06	Throttled	Tatum	getLatestBlockhash	4m	100%vs 99%
2026-10-08 01:37	Throttled	Tatum	getBlockHeight	3m	0%vs 100%
2026-10-08 01:07	Throttled	Tatum	getHealth	4m	0%vs 100%
2026-10-07 23:28	Throttled	Tatum	getBlockHeight	4m	100%vs 100%
2026-10-07 23:26	Degraded	PublicNode	getLatestBlockhash	10m	50%vs 99%
2026-10-07 23:18	Degraded	Tatum	getSlot	4m	67%vs 98%
2026-10-07 23:11	Degraded	PublicNode	getLatestBlockhash	12m	50%vs 99%
2026-10-07 22:20	Degraded	Tatum	getSlot	5m	60%vs 99%
2026-10-07 21:39	Throttled	Tatum	getSlot	12m	100%vs 98%
2026-10-07 21:37	Throttled	Tatum	getBlockHeight	4m	0%vs 100%
2026-10-07 20:40	Throttled	Tatum	getSlot	8m	100%vs 99%
2026-10-07 20:40	Degraded	Tatum	getSlot	3m	67%vs 98%
2026-10-07 20:37	Throttled	Tatum	getEpochInfo	10m	0%vs 97%
2026-10-07 20:11	Throttled	Tatum	getSlot	7m	100%vs 99%
2026-10-07 19:58	Throttled	Tatum	getLatestBlockhash	4m	100%vs 98%

Take it awayCSV JSONevery incident in this window, not only the filtered view

Persistent conditions

the same across the whole window

Calls a provider fails, or refuses, at about the same rate every day. Not events — the availability figure already carries them — but the thing most worth knowing before choosing a provider, because none of it will improve tomorrow.

Calls that consistently fail or are consistently refused
Provider	Call	Condition	Succeeds	Refused	Time affected
Tatum	getBalance	Throttled	—	100%	8m
Tatum	getBalance	Throttled	—	100%	6m

What got slower, and what got faster

against each provider’s own past

The last 24 hours against the 7 days before, per call. Compared against itself rather than against the field: the ranking already says who is slower than whom, and a provider that has always been the slowest is not regressing — it is slow.

Per-method latency changes over the last 24 hours against the 7 days before
Change	Provider	Call	Was	Now	Samples
-59%	PublicNodeSolana	getAccountInfo	121 ms	50 ms	2,777
-49%	PublicNodeSolana	getTransactionavailability moved too (76% → 71%)	122 ms	63 ms	554
-74%	PublicNodeSolana	getMultipleAccounts	221 ms	58 ms	1,112
-64%	PublicNodeSolana	getBlock	277 ms	100 ms	371

Take it awayCSV JSONevery change in this window, not only the filtered view

What counts, and what does not

Our own failures are not theirs

An agent that could not reach the network, or our own software failing, is our outage. Both are removed before anything is judged — the same exclusion the score makes.

Rate limiting is not failure

A provider enforcing its published limits is behaving correctly, so it has its own colour here. A sustained refusal is still reported, as throttling rather than as an outage.

Incidents are per method, not per provider

Rolling one failing call up to the provider manufactures outages: a single method erroring a fifth of the time drags a whole-provider success rate below any sensible threshold permanently.

A single bad minute is not an incident

One failed request is a blip. A run has to last long enough that somebody could have noticed — at least 3 minutes.

Durations are floors, never estimates

Only minutes with measurement behind them are counted, and a gap longer than the tolerance ends an incident rather than being spanned. An incident is never reported as longer than what was observed inside it.

A chronic defect is not an event

Judged against the series’ own rate across the whole window — the same principle the ranking applies to latency, where a provider consistently slower than its peers is slower rather than degraded.

Derived from per-minute measurement aggregates rather than stored, so this feed cannot describe something the observations do not. Our own failures — an agent that could not reach the network, our own software failing — are excluded: they are our outage, not the provider's. Rate limiting is reported as throttling rather than as failure, because a provider enforcing its published limits is behaving correctly. A single bad minute is not an incident, and an incident is measured per method: rolling one failing call up to the provider would report an outage for a provider that was serving everything else perfectly. An incident is never reported as longer than the minutes actually measured within it, so durations are floors rather than estimates. A series that fails at about the same rate all week is marked chronic and left out by default — it is broken rather than having an outage, which the availability figure already says, and treating it as news would bury the runs that are.