Skip to content

0x920f…6c1e

Range
Resolution

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

Acceptance rate

94.5%

25th of 34 · median 99.3%
Latency p95

1.15 s

24th of 30 · median 573 ms
Reported lag p95

9 s

10th of 30 · median 10 s
Attempts

74

4 failed · 0.1% of gateway attempts
Estimated receipt fees

≈ 0.02923 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
Success94.5% · Acceptance rate99.3%Weak
Latency324 ms · Mean of accepted attempts317 msFair
Time behind chain head6.67 s · Mean reported lag, zero readings excluded5.04 sFair

Success is this indexer's weakest observed factor

Repeated failures reduce selection quickly, and recovery after a fix is gradual. Start with the largest failure class below.

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-one74494.5%1.15 s9 s≈ 0.02923 GRT

1 deployment

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…)4100.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