Skip to content

0x1b7e…d98d

Range
Resolution

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

Acceptance rate

99.9%

5th of 34 · median 99.3%
Latency p95

2.13 s

28th of 30 · median 573 ms
Reported lag p95

15 s

23rd of 30 · median 10 s
Attempts

5.8K

5 failed · 10.5% of gateway attempts
Estimated receipt fees

≈ 2.317 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.9% · Acceptance rate99.3%Strong
Latency879 ms · Mean of accepted attempts317 msWeak
Time behind chain head6.86 s · Mean reported lag, zero readings excluded5.04 sFair

Latency is this indexer's weakest observed factor

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-one5.4K599.9%2.14 s2 s≈ 2.146 GRT
mainnet3880100.0%939 ms15 s≈ 0.171 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
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%
Bad response, otherThe gateway could not use the response, for another reason, such as a malformed body.Check: indexer-service logs for the query at that time.BadResponse(…)120.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