Skip to content

0xe9e2…cf59

Range
Resolution

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

Acceptance rate

99.2%

19th of 34 · median 99.3%
Latency p95

535 ms

13th of 30 · median 573 ms
Reported lag p95

8 s

8th of 30 · median 10 s
Attempts

1.6K

12 failed · 2.9% of gateway attempts
Estimated receipt fees

≈ 0.6495 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.2% · Acceptance rate99.3%Fair
Latency317 ms · Mean of accepted attempts317 msStrong
Time behind chain head4.08 s · Mean reported lag, zero readings excluded5.04 sStrong

Success is a little below the median indexer

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-one1.3K499.7%523 ms3 s≈ 0.55 GRT
mainnet2220100.0%301 ms8 s≈ 0.08967 GRT
arbitrum-one23769.5%20.1 s5 s≈ 0.009435 GRT
arbitrum-one110.0%UnavailableUnavailable≈ 0.0004156 GRT

1-4 of 4 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
TimeoutNo response before the gateway's timeout.Check: Slow queries or an overloaded Graph Node: compare your query latency at the same time.Timeout866.6%
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…)433.3%
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