Skip to content

0x38f4…27c0

Range
Resolution

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

Acceptance rate

86.4%

28th of 34 · median 99.3%
Latency p95

71 ms

1st of 30 · median 573 ms
Reported lag p95

12 s

18th of 30 · median 10 s
Attempts

5.7K

785 failed · 10.4% of gateway attempts
Estimated receipt fees

≈ 2.385 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
Success86.4% · Acceptance rate99.3%Weak
Latency48 ms · Mean of accepted attempts317 msStrong
Time behind chain head2.79 s · Mean reported lag, zero readings excluded5.04 sStrong

Success is this indexer's weakest observed factor

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-one4.5K78482.8%70 ms3 s≈ 1.824 GRT
mainnet662199.8%75 ms11 s≈ 0.2984 GRT
mainnet5340100.0%70 ms15 s≈ 0.2575 GRT
mainnet50100.0%1.24 sUnavailable≈ 0.001964 GRT
arbitrum-sepolia30100.0%307 msUnavailable≈ 0.001582 GRT
arbitrum-sepolia20100.0%73 ms1 s≈ 0.001027 GRT

1-6 of 6 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…)78399.7%
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(…)20.2%
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