Skip to content

0xf92f…a6d4

Range
Resolution

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

Acceptance rate

99.8%

6th of 34 · median 99.3%
Latency p95

755 ms

18th of 30 · median 573 ms
Reported lag p95

14 s

21st of 30 · median 10 s
Attempts

3.6K

4 failed · 6.5% of gateway attempts
Estimated receipt fees

≈ 1.514 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.8% · Acceptance rate99.3%Strong
Latency317 ms · Mean of accepted attempts317 msFair
Time behind chain head4.18 s · Mean reported lag, zero readings excluded5.04 sStrong

Latency is a little below the median indexer

Only successful responses count toward latency, and a request that times out after 20 seconds counts as a failure.

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-one2.7K499.8%619 ms3 s≈ 1.1 GRT
mainnet5360100.0%143 ms12 s≈ 0.2587 GRT
mainnet2390100.0%1.38 s15 s≈ 0.11 GRT
arbitrum-one870100.0%1.16 s5 s≈ 0.03899 GRT
mainnet50100.0%2.94 sUnavailable≈ 0.001964 GRT
arbitrum-sepolia30100.0%128 ms1 s≈ 0.001582 GRT
arbitrum-sepolia20100.0%232 msUnavailable≈ 0.001027 GRT
arbitrum-one20100.0%128 msUnavailable≈ 0.0008292 GRT
arbitrum-one10100.0%13.38 sUnavailable≈ 0.0004156 GRT
arbitrum-one10100.0%1.12 sUnavailable≈ 0.0006251 GRT

1-10 of 10 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…)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.1Not applicable