Skip to content

0x4d67…c659

Range
Resolution

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

Acceptance rate

99.3%

17th of 34 · median 99.3%
Latency p95

90 ms

2nd of 30 · median 573 ms
Reported lag p95

16 s

24th of 30 · median 10 s
Attempts

785

5 failed · 1.4% of gateway attempts
Estimated receipt fees

≈ 0.316 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.3% · Acceptance rate99.3%Strong
Latency74 ms · Mean of accepted attempts317 msStrong
Time behind chain head5.43 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-one784599.3%90 ms7 s≈ 0.3156 GRT
mainnet10100.0%48 ms16 s≈ 0.0003873 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…)5100.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