Skip to content

0x9af3…f0d0

Range
Resolution

2026-11-19 20:00 – 2026-11-20 20:00 UTC · Link to this exact range

Acceptance rate

99.6%

12th of 34 · median 99.3%
Latency p95

595 ms

16th of 30 · median 573 ms
Reported lag p95

10 s

13th of 30 · median 10 s
Attempts

1.5K

5 failed · 2.7% of gateway attempts
Estimated receipt fees

≈ 0.6099 GRT

Not settled revenue

Observed selection factors

Observed from this range's data and set beside the median indexer on the same slice. The gateway weighs recent results differently, so an observed band is not the score the gateway used. Stake and fee also count and are not shown. How selection works

FactorObservedMedian indexerObserved bandActions
Success99.6% · Acceptance rate99.3%Strong
Latency312 ms · Mean of accepted attempts317 msStrong
Time behind chain head5.73 s · Mean reported lag, zero readings excluded5.04 sFair

Time behind chain head is a little below the median indexer

For queries that want the latest data, the gateway prefers indexers closer to chain head, and skips one more than 30 minutes behind whenever another is within 30 minutes.

Over time

Percentiles are approximate. Times are UTC; gaps are intervals without observations.

Acceptance rate
Latency, accepted attempts
Attempts
Reported lag

Deployments

Deployment CIDNetworkAttemptsFailuresAcceptance rateLatency p95Reported lag p95Estimated receipt feesActions
arbitrum-one1.3K499.6%607 ms3 s≈ 0.5231 GRT
mainnet2060100.0%275 ms10 s≈ 0.08205 GRT
arbitrum-one12191.6%17.79 s7 s≈ 0.004744 GRT

1-3 of 3 deployments

Rows
Page 1 of 1

Failures

Why this indexer's attempts failed. A failed attempt does not always fail a client's query: the gateway can answer it from another indexer.

FailureWhat it means and what to checkCountShare of failuresActions
Missing blockYour indexer reported it has not indexed the block the query needs.Check: Sync progress on the deployment and whether it was pruned below the queried block.Unavailable(missing block…)480.0%
TimeoutNo response before the gateway's timeout.Check: Slow queries or an overloaded Graph Node: compare your query latency at the same time.Timeout120.0%
Accepted with error textAccepted, but the response carried GraphQL error text. Not counted as a failure.Check: The GraphQL errors your Subgraph returns for these queries.0Not applicable