Skip to content

0xedca…2beb

Range
Resolution

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

Acceptance rate

100.0%

1st of 34 · median 99.3%
Latency p95

210 ms

9th of 30 · median 573 ms
Reported lag p95

9 s

10th of 30 · median 10 s
Attempts

377

0 failed · 0.6% of gateway attempts
Estimated receipt fees

≈ 0.1719 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
Success100.0% · Acceptance rate99.3%Strong
Latency154 ms · Mean of accepted attempts317 msStrong
Time behind chain head4.63 s · Mean reported lag, zero readings excluded5.04 sStrong

Every observed factor is at or better than the median indexer

Stake and fee also count toward selection, and this data does not include them.

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
mainnet3760100.0%210 ms9 s≈ 0.1715 GRT
arbitrum-one10100.0%133 msUnavailable≈ 0.0004146 GRT

1-2 of 2 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
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.1Not applicable